Triple
T12603612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de la Roche dynasty |
E300917
|
entity |
| Predicate | endOfRuleCentury |
P31300
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [de la Roche dynasty, endOfRuleCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfRuleCentury Context triple: [de la Roche dynasty, endOfRuleCentury, 14th century]
-
A.
ruledUntilCentury
chosen
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
-
B.
ruledFromCentury
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
-
C.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
D.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
E.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:10 p.m.