Triple
T7513798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperium Romaniae |
E177589
|
entity |
| Predicate | capitalRecapturedIn |
P77403
|
FINISHED |
| Object | 1261 |
—
|
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: 1261 | Statement: [Imperium Romaniae, capitalRecapturedIn, 1261]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRecapturedIn Context triple: [Imperium Romaniae, capitalRecapturedIn, 1261]
-
A.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
B.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
C.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
D.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
-
E.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d6ccb08190a568a9b58bfbd0cc |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:45 p.m.