Triple
T30943590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Cities of America |
E788325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political entity in a video game |
C5423
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: political entity in a video game Context triple: [United Cities of America, instanceOf, political entity in a video game]
-
A.
political entity
A political entity is an organized group or jurisdiction, such as a state, nation, or governing body, that holds authority to make and enforce collective decisions over a defined population and territory.
-
B.
political entity category
A political entity category is a conceptual classification that groups together types of organized political units—such as states, provinces, municipalities, or international organizations—based on shared structural, legal, or functional characteristics.
-
C.
video game fictional entity
chosen
A video game fictional entity is any imagined character, creature, object, or construct that exists within the narrative or interactive world of a video game, defined by its designed attributes, behaviors, and role in gameplay or story.
-
D.
collective political entity
A collective political entity is an organized group of individuals or communities that exercises or claims shared authority, representation, and decision-making power within a defined political framework.
-
E.
ancient political entity
An ancient political entity is a historically situated, organized community or state that exercised authority, governance, and control over a defined territory and population in antiquity.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 29, 2026, 8:53 p.m.