Triple
T7077937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Eagle |
E164867
|
entity |
| Predicate | temporarilyRestoredInYear |
P65133
|
FINISHED |
| Object | 1815 |
—
|
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: 1815 | Statement: [Imperial Eagle, temporarilyRestoredInYear, 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyRestoredInYear Context triple: [Imperial Eagle, temporarilyRestoredInYear, 1815]
-
A.
temporarilyRestored
chosen
Indicates that a previously unavailable or altered state, condition, or connection has been brought back to its former status for a limited or non-permanent period.
-
B.
replacedInYear
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
C.
rescueYear
Indicates the year in which a rescue event involving the entity took place.
-
D.
recombinedInYear
Indicates that an entity was recombined, reclassified, or reassigned in a particular year.
-
E.
returnedToManagingYear
Indicates that an entity has resumed or gone back to a previously assigned managing year after a change or interruption.
- 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ee29288190a9a3fa7a6c713d8f |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.