Triple
T5242892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michel Ney |
E118385
|
entity |
| Predicate | createdPrinceOfTheMoskowa |
P62346
|
FINISHED |
| Object | 1813 |
—
|
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: 1813 | Statement: [Michel Ney, createdPrinceOfTheMoskowa, 1813]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPrinceOfTheMoskowa Context triple: [Michel Ney, createdPrinceOfTheMoskowa, 1813]
-
A.
coPrince
Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
-
B.
reignAsGrandPrinceOfMoscowFrom
Indicates that a person held the position of Grand Prince of Moscow starting from a specified time.
-
C.
reignAsGrandPrinceOfVladimirFrom
Indicates that a person held the position of Grand Prince of Vladimir starting from a specified time.
-
D.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
E.
viewOfPrince
Indicates a visual representation or perspective specifically depicting the prince.
- F. None of above. chosen
Provenance (4 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79e9d794819097bb628c603d14af |
completed | March 20, 2026, 4:46 p.m. |
Created at: March 20, 2026, 1:49 p.m.