Triple
T31943852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_tb |
E815594
|
entity |
| Predicate | couplesQuarks |
P173476
|
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_tb, couplesQuarks, top quark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couplesQuarks Context triple: [V_tb, couplesQuarks, top quark]
-
A.
couplesTo
Indicates that one entity is joined or linked to another in a way that allows interaction, transfer, or mutual influence between them.
-
B.
notableCouple
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
-
C.
spouseInDuo
Indicates that two individuals are spouses who perform or appear together as a duo.
-
D.
courtships
Indicates that one entity engages in courtship behavior toward another, typically as part of initiating or maintaining a romantic or mating relationship.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- F. None of above. chosen
Provenance (4 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_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:06 a.m.