Triple
T30569512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Some Luck |
E778085
|
entity |
| Predicate | narrativeStartYear |
P70694
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Some Luck, narrativeStartYear, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeStartYear Context triple: [Some Luck, narrativeStartYear, 1920]
-
A.
narrativeStart
Indicates the point or event at which a narrative, story, or sequence of events begins.
-
B.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
C.
narratedPeriodStart
chosen
Indicates the point in time at which the narrated or described period begins.
-
D.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
foundedInNarrative
Indicates that an entity is established or created within the context of a specific narrative or story, rather than in real-world history.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:21 p.m.