Triple
T30943123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Knot City |
E788314
|
entity |
| Predicate | infrastructureInFiction |
P120608
|
FINISHED |
| Object | chiral network terminals |
—
|
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: chiral network terminals | Statement: [Capital Knot City, infrastructureInFiction, chiral network terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureInFiction Context triple: [Capital Knot City, infrastructureInFiction, chiral network terminals]
-
A.
architectInFiction
Indicates that an entity appears as an architect within a fictional work or narrative context.
-
B.
partOfFictionalCityInfrastructure
chosen
Indicates that something is a component or subsystem within the constructed infrastructure of a fictional city.
-
C.
fictionalBuilding
Indicates that a building is imaginary or exists only within a fictional or invented context.
-
D.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
-
E.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:53 p.m.