Triple
T33916940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euphegenia Doubtfire |
E869484
|
entity |
| Predicate | fictionalAgeAppearance |
P99186
|
FINISHED |
| Object | elderly |
—
|
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: elderly | Statement: [Euphegenia Doubtfire, fictionalAgeAppearance, elderly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalAgeAppearance Context triple: [Euphegenia Doubtfire, fictionalAgeAppearance, elderly]
-
A.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
B.
fictionalAgeRange
Indicates the span of ages a fictional character or entity is depicted as having within a narrative or fictional context.
-
C.
fictionalAgeStage
chosen
Indicates the stage or phase of life a fictional character is in within a narrative or imagined context.
-
D.
existsInFictionalTimePeriod
Indicates that an entity is situated within, or associated with, a time period that is fictional rather than part of real-world history.
-
E.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 1:48 a.m.