Triple
T440338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma! (1955 film) |
E10099
|
entity |
| Predicate | setInTime |
P4815
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Oklahoma! (1955 film), setInTime, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInTime Context triple: [Oklahoma! (1955 film), setInTime, early 20th century]
-
A.
setInEvent
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
B.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
-
C.
representsTimeIn
chosen
Indicates that one entity expresses, encodes, or specifies the time at which another entity occurs, is valid, or is observed.
-
D.
setInState
Indicates that an entity is located within, or belongs to, a particular state or state-level jurisdiction.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.