Triple
T25953344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethel Lodore |
E654022
|
entity |
| Predicate | hasFictionalEra |
P18945
|
FINISHED |
| Object | early 19th 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 19th century | Statement: [Ethel Lodore, hasFictionalEra, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalEra Context triple: [Ethel Lodore, hasFictionalEra, early 19th century]
-
A.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
B.
endsInFictionalYear
Indicates that an event, story, or timeline concludes in a year that exists only within a fictional or imagined setting.
-
C.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
D.
hasFictionalScope
Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
-
E.
hasFictionalUniverseGenre
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 22, 2026, 8:44 a.m.