Triple
T8319105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firestarter |
E194782
|
entity |
| Predicate | fictionalOrganizationType |
P81118
|
FINISHED |
| Object | secret government agency |
—
|
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: secret government agency | Statement: [Firestarter, fictionalOrganizationType, secret government agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalOrganizationType Context triple: [Firestarter, fictionalOrganizationType, secret government agency]
-
A.
fictionalOrganizationFeatured
Indicates that a fictional organization is prominently presented or plays a significant role within a given work or context.
-
B.
fictionalEntityType
chosen
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
C.
fictionalOrganizationName
Indicates that the relationship specifies the name assigned to a fictional organization.
-
D.
creatorOrganizationType
Indicates the type or category of organization that created or is responsible for the entity.
-
E.
foundedOrganizationType
Indicates that an entity established or created an organization of a specified type (e.g., company, nonprofit, institution).
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f648e10819081ad1fed870b2b86 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.