Triple
T32286410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oskar Werner as Jules |
E824841
|
entity |
| Predicate | setAroundEvent |
P2808
|
FINISHED |
| Object | World War I |
—
|
NE NERFINISHED |
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: World War I | Statement: [Oskar Werner as Jules, setAroundEvent, World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAroundEvent Context triple: [Oskar Werner as Jules, setAroundEvent, World War I]
-
A.
setAround
Indicates that one entity is positioned or arranged surrounding another entity or a central point.
-
B.
setAroundHoliday
Indicates that something is scheduled, arranged, or configured to occur in the time period surrounding a holiday.
-
C.
endAround
Indicates that an event, process, or state concludes approximately at a specified time, location, or condition rather than at an exact, sharply defined endpoint.
-
D.
setInEvent
chosen
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
E.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccf68b0819096225377b8130beb |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.