Triple
T3483159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Etruria |
E73541
|
entity |
| Predicate | predecessorStateForm |
P49038
|
FINISHED |
| Object | grand duchy |
—
|
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: grand duchy | Statement: [Kingdom of Etruria, predecessorStateForm, grand duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorStateForm Context triple: [Kingdom of Etruria, predecessorStateForm, grand duchy]
-
A.
predecessorState
Indicates that one state directly precedes another in a sequence or process.
-
B.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
C.
predecessorStateConcerned
Indicates that a concern or issue present in a predecessor state is relevant to, or carried over into, the current state.
-
D.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
E.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb781e9c8190810fdd814f506127 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.