Triple
T27102302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Skull |
E686472
|
entity |
| Predicate | fictionalUniverseChronology |
P18945
|
FINISHED |
| Object | set in 1957 |
—
|
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: set in 1957 | Statement: [Crystal Skull, fictionalUniverseChronology, set in 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalUniverseChronology Context triple: [Crystal Skull, fictionalUniverseChronology, set in 1957]
-
A.
fictionalUniverseEvent
Indicates an event or occurrence that takes place within a specific fictional universe or narrative continuity.
-
B.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
C.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
D.
fictionalTime
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
E.
fictionalUniverseDebut
Indicates the first appearance of an entity within a particular fictional 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 8:48 a.m.