Triple
T37770506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon V |
E941532
|
entity |
| Predicate | controlledByInFiction |
P93991
|
FINISHED |
| Object | shadow government agencies |
—
|
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: shadow government agencies | Statement: [Weapon V, controlledByInFiction, shadow government agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByInFiction Context triple: [Weapon V, controlledByInFiction, shadow government agencies]
-
A.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
-
B.
guardedByInFiction
Indicates that one fictional entity is protected or watched over by another within a narrative context.
-
C.
governedByFictional
Indicates that one entity is under the rule, control, or authority of another entity that is fictional or exists only in an imagined context.
-
D.
managedByFictionalCharacter
Indicates that an entity is overseen, directed, or run under the authority or control of a fictional character.
-
E.
hasControllerInFiction
chosen
Indicates that an entity is under the control or direction of a specified controller within a fictional context or narrative.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:19 p.m.