Triple
T2208681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum chromodynamics |
E50861
|
entity |
| Predicate | hasForceCarrier |
P37471
|
FINISHED |
| Object | gluon |
—
|
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: gluon | Statement: [quantum chromodynamics, hasForceCarrier, gluon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForceCarrier Context triple: [quantum chromodynamics, hasForceCarrier, gluon]
-
A.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
D.
hasReserveForces
Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
-
E.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc1b912c08190b9d7bc9230e49d1d |
completed | March 7, 2026, 6:12 a.m. |
Created at: March 4, 2026, 7:46 p.m.