Triple
T5406348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berthold V, Duke of Zähringen |
E120900
|
entity |
| Predicate | causeOfLineEnd |
P54944
|
FINISHED |
| Object | death without male heir |
—
|
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: death without male heir | Statement: [Berthold V, Duke of Zähringen, causeOfLineEnd, death without male heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLineEnd Context triple: [Berthold V, Duke of Zähringen, causeOfLineEnd, death without male heir]
-
A.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
C.
endLineUsage
Indicates the relationship where a particular line or resource is used up to or at its terminating point or final extent.
-
D.
reasonForEndOfRule
chosen
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
E.
lineTerminusFor
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
- F. None of above.
Provenance (3 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87924c588190beb4a1be27f8d11b |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.