Triple
T1484776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom Triumphant in War and Peace |
E29439
|
entity |
| Predicate | installationDate |
P25196
|
FINISHED |
| Object | 1863 |
—
|
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: 1863 | Statement: [Freedom Triumphant in War and Peace, installationDate, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationDate Context triple: [Freedom Triumphant in War and Peace, installationDate, 1863]
-
A.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
B.
yearOfOriginalInstallation
chosen
Indicates the specific calendar year when something was first installed or put into initial operation.
-
C.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
D.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
E.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a011f0819086e9ee517ed6d29f |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.