Triple
T33431931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarati |
E856152
|
entity |
| Predicate | inUniverseUsePeriod |
P179948
|
FINISHED |
| Object | Elder Days |
—
|
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: Elder Days | Statement: [Sarati, inUniverseUsePeriod, Elder Days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseUsePeriod Context triple: [Sarati, inUniverseUsePeriod, Elder Days]
-
A.
inUniversePeriod
chosen
Indicates that something exists, occurs, or is valid within a specified time period in a particular fictional or conceptual universe.
-
B.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
C.
inUniverseUseRestriction
Indicates that the use of something is restricted or limited within a specific fictional or defined universe or setting.
-
D.
inUniverseActivity
Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
-
E.
inUniverseRestriction
Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 1, 2026, 1:36 a.m.