Triple
T14702618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady |
E345343
|
entity |
| Predicate | timeSettingInFiction |
P11197
|
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: [Lady, timeSettingInFiction, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSettingInFiction Context triple: [Lady, timeSettingInFiction, early 20th century]
-
A.
fictionalTime
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
B.
fictionalTimeDepth
Indicates a relationship where an entity is associated with a time period or temporal depth that exists only within a fictional or imagined context.
-
C.
laterSettingOfFiction
Indicates that one fictional work is set chronologically later than another within a shared narrative or story world.
-
D.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
E.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb6071e5c8190bb5509c859135c2d |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.