Triple
T19557694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry II, Count of Champagne |
E489359
|
entity |
| Predicate | ruledTo |
P60298
|
FINISHED |
| Object | 1197 |
—
|
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: 1197 | Statement: [Henry II, Count of Champagne, ruledTo, 1197]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledTo Context triple: [Henry II, Count of Champagne, ruledTo, 1197]
-
A.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
B.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
C.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
D.
ruledLaterBy
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
E.
rulerOf
chosen
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d34d1bc81908e5e10f069655866 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.