Triple
T30943614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Cities of America |
E788325
|
entity |
| Predicate | governedByFictionalOrganization |
P61128
|
FINISHED |
| Object | Bridges |
—
|
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: Bridges | Statement: [United Cities of America, governedByFictionalOrganization, Bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByFictionalOrganization Context triple: [United Cities of America, governedByFictionalOrganization, Bridges]
-
A.
worksForFictionalOrganization
Indicates that an entity is employed by or affiliated as a worker with a fictional organization.
-
B.
governedByFictional
chosen
Indicates that one entity is under the rule, control, or authority of another entity that is fictional or exists only in an imagined context.
-
C.
fictionalUniverseOrganizationLed
Indicates that an organization is led or headed by a particular entity within a fictional universe.
-
D.
worksAtFictionalPlace
Indicates that an entity is employed at or associated with performing work in a fictional or imaginary location.
-
E.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
- 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_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: April 29, 2026, 8:53 p.m.