Triple
T5297320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Kingdom of Poland (1815) |
E119885
|
entity |
| Predicate | replacementYear |
P36106
|
FINISHED |
| Object | 1832 |
—
|
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: 1832 | Statement: [Constitution of the Kingdom of Poland (1815), replacementYear, 1832]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacementYear Context triple: [Constitution of the Kingdom of Poland (1815), replacementYear, 1832]
-
A.
replacedInYear
chosen
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
B.
replacementDate
Indicates the date on which something is replaced or scheduled to be replaced.
-
C.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
D.
returnYear
Indicates the year in which something is returned or given back to its original owner, place, or state.
-
E.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.