Triple
T4720901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh of Vermandois |
E104761
|
entity |
| Predicate | deathDateApproximation |
P26944
|
FINISHED |
| Object | 18th century chroniclers place his death in 1101 |
—
|
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: 18th century chroniclers place his death in 1101 | Statement: [Hugh of Vermandois, deathDateApproximation, 18th century chroniclers place his death in 1101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathDateApproximation Context triple: [Hugh of Vermandois, deathDateApproximation, 18th century chroniclers place his death in 1101]
-
A.
dateOfDeath
Indicates the specific date on which an individual or entity died.
-
B.
deathYearApproximate
chosen
Indicates that the year of an entity’s death is known only approximately rather than as an exact calendar year.
-
C.
deathDateEvent
Indicates the date on which a death occurred or a death-related event took place.
-
D.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
-
E.
dateOfPassage
Indicates the specific calendar date on which a law, bill, or formal measure was officially approved or enacted.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.