Triple
T24711185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Systems Red |
E612029
|
entity |
| Predicate | hasFictionalCorporation |
P158093
|
FINISHED |
| Object | The Company |
—
|
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: The Company | Statement: [All Systems Red, hasFictionalCorporation, The Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalCorporation Context triple: [All Systems Red, hasFictionalCorporation, The Company]
-
A.
hasFictionalParentCompany
Indicates that an entity is associated with a parent company that exists only in a fictional or imaginary context.
-
B.
hasFictionalProductionCompany
Indicates that one entity is associated with or owns a production company that exists only within a fictional context.
-
C.
fictionalCorporation
Indicates that an entity is a corporation that exists only in fiction rather than in the real world.
-
D.
worksForFictionalOrganization
Indicates that an entity is employed by or affiliated as a worker with a fictional organization.
-
E.
hasFictionalBusinessType
Indicates that an entity is associated with a type or category of fictional business it operates or represents.
- F. None of above. chosen
Provenance (4 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 3:24 a.m.