Triple
T3921377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermion |
E88965
|
entity |
| Predicate | hasGenerations |
P52584
|
FINISHED |
| Object | Three generations of quarks |
—
|
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: Three generations of quarks | Statement: [Fermion, hasGenerations, Three generations of quarks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenerations Context triple: [Fermion, hasGenerations, Three generations of quarks]
-
A.
hasGenerationRelationship
Indicates that one entity is involved in producing, creating, or giving rise to another entity.
-
B.
multiGenerationControl
Indicates a relationship where one entity exercises control or influence over multiple successive generations of another entity or group.
-
C.
hasNumberOfForfeda
Indicates a relationship where an entity is associated with a specific count of forfeda (additional Ogham letters).
-
D.
generationOf
Indicates that one entity is the origin, creator, or producer of another entity.
-
E.
multiGenerationOwnershipOf
Indicates that ownership of something extends across multiple generations within the same family or lineage.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef18748648190b85e62f7796ff4b4 |
completed | March 9, 2026, 4:12 p.m. |
Created at: March 9, 2026, 3:22 p.m.