Triple
T36987487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quality Road |
E915002
|
entity |
| Predicate | hasProgenyIn |
P173350
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [Quality Road, hasProgenyIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgenyIn Context triple: [Quality Road, hasProgenyIn, United States]
-
A.
hasProgenitorType
Indicates that an entity originates from, or is derived from, a specified type of progenitor or source.
-
B.
hasChildIn
chosen
Indicates that one entity has a child who is located in, associated with, or present within another specified entity or context.
-
C.
hasChildrenWith
Indicates that two entities share one or more biological or adopted children together.
-
D.
hasHierarchyIn
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
-
E.
has child
Indicates that one entity is the parent of another entity, which is its child.
- F. None of above.
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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402b9788e48190aded4f313d09d56a |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.