Triple
T23515550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONTROL |
E574352
|
entity |
| Predicate | fictionalRivalOrganization |
P103334
|
FINISHED |
| Object | KAOS |
—
|
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: KAOS | Statement: [CONTROL, fictionalRivalOrganization, KAOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRivalOrganization Context triple: [CONTROL, fictionalRivalOrganization, KAOS]
-
A.
fictionalRivalOf
chosen
Indicates a rivalry relationship that exists between two entities only within a fictional or narrative context.
-
B.
fictionalCorporation
Indicates that an entity is a corporation that exists only in fiction rather than in the real world.
-
C.
fictionalCompetitorType
Indicates that one fictional entity is characterized as a competitor of a specified type relative to another fictional entity or context.
-
D.
worksForFictionalOrganization
Indicates that an entity is employed by or affiliated as a worker with a fictional organization.
-
E.
fictionalOrganizationFeatured
Indicates that a fictional organization is prominently presented or plays a significant role within a given work or context.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa81ab4c8190b85c8f80754020ea |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.