Triple
T29548448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Works industrial district |
E749692
|
entity |
| Predicate | inUniversePlanetTypeContext |
P62562
|
FINISHED |
| Object | ecumenopolis |
—
|
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: ecumenopolis | Statement: [Works industrial district, inUniversePlanetTypeContext, ecumenopolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniversePlanetTypeContext Context triple: [Works industrial district, inUniversePlanetTypeContext, ecumenopolis]
-
A.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
B.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
C.
inUniverseDesignation
Indicates that an entity’s name or label is the one used within the fictional universe itself, as opposed to an external or real-world designation.
-
D.
hasCentralPlanetType
Indicates that an entity has a central planet whose type or classification is specified by the related value.
-
E.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 5:10 p.m.