Triple
T17884651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormwatch |
E447169
|
entity |
| Predicate | teamStatusInFiction |
P58920
|
FINISHED |
| Object | global security force |
—
|
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: global security force | Statement: [Stormwatch, teamStatusInFiction, global security force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamStatusInFiction Context triple: [Stormwatch, teamStatusInFiction, global security force]
-
A.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
B.
stateInFiction
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
-
C.
in-universeStatus
chosen
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
-
D.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
E.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c11530881908ad98fbd0a52b1c3 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.