Triple
T37357758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozart family |
E927499
|
entity |
| Predicate | hasLineageEnd |
P198913
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Mozart family, hasLineageEnd, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineageEnd Context triple: [Mozart family, hasLineageEnd, 19th century]
-
A.
hasLineageStart
Indicates that an entity originates from, or traces its lineage back to, a specified starting ancestor or source in a lineage chain.
-
B.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
C.
hasLineageStatus
Indicates the lineage or ancestry classification assigned to an entity, such as whether and how it descends from or is derived from another.
-
D.
hasLeaderLineage
Indicates that an entity’s lineage or ancestry includes one or more individuals who have held a leadership role.
-
E.
hasLineageName
Indicates that an entity is associated with or identified by a specific lineage name within a genealogical or hierarchical context.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
| PDg | Predicate description generation | batch_69ff136c68b481909b83d5b8a3693622 |
completed | May 9, 2026, 10:58 a.m. |
Created at: May 3, 2026, 4:16 p.m.