Triple
T31943804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_ts |
E815593
|
entity |
| Predicate | describesCouplingBetween |
P31186
|
FINISHED |
| Object | top quark |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: top quark | Statement: [V_ts, describesCouplingBetween, top quark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesCouplingBetween Context triple: [V_ts, describesCouplingBetween, top quark]
-
A.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
B.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
C.
hasCouplingConstant
chosen
Indicates that one entity is associated with a specific coupling constant value that quantifies the strength of an interaction or relationship.
-
D.
definesCollaborationBetween
Indicates that one entity specifies or establishes the terms or existence of a collaborative relationship between two or more entities.
-
E.
hasCouplers
Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:06 a.m.