Triple
T7950839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marion Hill |
E184608
|
entity |
| Predicate | activeInFictionalUniverse |
P79039
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Marion Hill, activeInFictionalUniverse, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInFictionalUniverse Context triple: [Marion Hill, activeInFictionalUniverse, 1990s]
-
A.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
portraysFictionalUniverse
Indicates that one entity depicts, represents, or presents the fictional universe in which another entity is set.
-
C.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
D.
hasFictionalUniverseGenre
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
-
E.
in-universeStatus
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
- F. None of above. chosen
Provenance (4 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5b7450819091e4e6f21e9d832d |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf632a924819086ac2336165f8da9 |
completed | March 30, 2026, 10:16 p.m. |
Created at: March 30, 2026, 5:10 p.m.