Triple
T5384840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Army Plaza |
E113177
|
entity |
| Predicate | archCompletionDate |
P62932
|
FINISHED |
| Object | 1892 |
—
|
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: 1892 | Statement: [Grand Army Plaza, archCompletionDate, 1892]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archCompletionDate Context triple: [Grand Army Plaza, archCompletionDate, 1892]
-
A.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
-
E.
approximateYearOfCompletion
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f5a7388190aa4ba2052afca74e |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:03 p.m.