Triple
T1676149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the White Eagle (Poland) |
E36234
|
entity |
| Predicate | reinstatedInYear |
P9113
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Order of the White Eagle (Poland), reinstatedInYear, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinstatedInYear Context triple: [Order of the White Eagle (Poland), reinstatedInYear, 1921]
-
A.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
B.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
D.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
-
E.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.