Triple
T28038605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas |
E708476
|
entity |
| Predicate | taskGiverInFiction |
P163653
|
FINISHED |
| Object | GLaDOS |
—
|
NE NERFINISHED |
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: GLaDOS | Statement: [Atlas, taskGiverInFiction, GLaDOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskGiverInFiction Context triple: [Atlas, taskGiverInFiction, GLaDOS]
-
A.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
B.
fictionalCharacterAssisted
Indicates that one fictional character provided help, support, or assistance to another fictional character.
-
C.
targetInFiction
Indicates that one entity is the target or subject of an action, focus, or effect within a fictional work or narrative context.
-
D.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
-
E.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63f2e1a248190a41f02f91e8c1183 |
completed | May 2, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:23 p.m.