Triple
T35062565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri, Count of Chambord |
E1011632
|
entity |
| Predicate | offeredThronePeriod |
P95976
|
FINISHED |
| Object | early 1870s |
—
|
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: early 1870s | Statement: [Henri, Count of Chambord, offeredThronePeriod, early 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredThronePeriod Context triple: [Henri, Count of Chambord, offeredThronePeriod, early 1870s]
-
A.
coronationPeriod
Indicates the time span during which a coronation event takes place or is in effect.
-
B.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
C.
possibleReignPeriod
chosen
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
-
D.
reignOrLeadershipPeriod
Indicates the time span during which an entity holds ruling authority or leadership over a group, organization, or territory.
-
E.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.