Triple
T35709281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Théâtre Optique |
E1031807
|
entity |
| Predicate | operationalPeriodApprox |
P203435
|
FINISHED |
| Object | 1892–1900s |
—
|
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–1900s | Statement: [Théâtre Optique, operationalPeriodApprox, 1892–1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalPeriodApprox Context triple: [Théâtre Optique, operationalPeriodApprox, 1892–1900s]
-
A.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operatingMonthsApproximate
Indicates that the time period during which something operates is specified in approximate months rather than exact dates.
-
C.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
operatedYearRound
Indicates that the subject entity functioned or was in operation continuously throughout the entire year, without seasonal closure.
-
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. 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a017d27e184819094638c3cf6876de4 |
completed | May 11, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_6a017c785a44819083111384b55769e9 |
completed | May 11, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_6a017d270e9881909e70280ff4e45e9a |
completed | May 11, 2026, 6:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.