Triple
T28038645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-body |
E708477
|
entity |
| Predicate | supervisedByInUniverse |
P117528
|
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: [P-body, supervisedByInUniverse, GLaDOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisedByInUniverse Context triple: [P-body, supervisedByInUniverse, GLaDOS]
-
A.
supervisesBy
Indicates that one entity is overseen, directed, or managed under the authority of another entity.
-
B.
managedByFictionalCharacter
chosen
Indicates that an entity is overseen, directed, or run under the authority or control of a fictional character.
-
C.
masteredBy
Indicates that a subject (such as a skill, topic, or resource) has been fully learned, controlled, or become highly proficiently used by a particular agent or entity.
-
D.
followsInUniverse
Indicates that one entity chronologically or logically comes after another within a specific fictional or defined universe or continuity.
-
E.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.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:23 p.m.