Triple
T37044959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Zutphen |
E916878
|
entity |
| Predicate | titleEndedBy |
P3587
|
FINISHED |
| Object | integration into Duchy of Guelders |
—
|
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: integration into Duchy of Guelders | Statement: [Count of Zutphen, titleEndedBy, integration into Duchy of Guelders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleEndedBy Context triple: [Count of Zutphen, titleEndedBy, integration into Duchy of Guelders]
-
A.
titleEndedOn
Indicates that a particular title or position held by an entity ceased or officially ended on a specified date.
-
B.
titleHolderEnd
Indicates the point in time or event at which an entity’s status as a title holder or champion comes to an end.
-
C.
titleLineageEndedWith
Indicates that a particular title’s hereditary succession or lineage has come to a definitive end with a specified holder or point in time.
-
D.
endedWith
chosen
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
E.
directorEnd
Indicates that a person’s role as a director of an entity has concluded at a specified time or event.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:14 p.m.