Triple
T10535446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Museum Panorama of the City of New York |
E248550
|
entity |
| Predicate | updatedFor |
P85673
|
FINISHED |
| Object | 1970s urban changes |
—
|
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: 1970s urban changes | Statement: [Queens Museum Panorama of the City of New York, updatedFor, 1970s urban changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedFor Context triple: [Queens Museum Panorama of the City of New York, updatedFor, 1970s urban changes]
-
A.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
B.
updateFor
chosen
Indicates that one entity is modified or refreshed in response to changes or conditions associated with another entity.
-
C.
updatedFrom
Indicates that one entity is a newer or modified version derived from another earlier entity.
-
D.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
E.
updatedEvery
Indicates that something is refreshed or brought up to date at a regular, specified interval.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a1b20d48190a51358ec1af80371 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.