Triple
T37510166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York World's Fair Corporation |
E932194
|
entity |
| Predicate | operatedInTimeSpan |
P802
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [New York World's Fair Corporation, operatedInTimeSpan, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInTimeSpan Context triple: [New York World's Fair Corporation, operatedInTimeSpan, 1930s]
-
A.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operationalPeriodApprox
Indicates that the time span during which something was in operation is known only approximately rather than as an exact period.
-
C.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
E.
historicallyOperatedOn
Indicates that an entity has, at some point in the past, performed an operation or action upon another entity.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0301c45274819083b0dd9d335f7ee0 |
completed | May 12, 2026, 10:32 a.m. |
| PD | Predicate disambiguation | batch_6a03015c272481908a7bfe81befb1764 |
completed | May 12, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:17 p.m.