Triple
T33691903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Capital |
E863205
|
entity |
| Predicate | worldbuildingDevice |
P135746
|
FINISHED |
| Object | tool to highlight internal divisions in a fictional world |
—
|
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: tool to highlight internal divisions in a fictional world | Statement: [Southern Capital, worldbuildingDevice, tool to highlight internal divisions in a fictional world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldbuildingDevice Context triple: [Southern Capital, worldbuildingDevice, tool to highlight internal divisions in a fictional world]
-
A.
worldbuildingFunction
chosen
Indicates the role or purpose something serves in constructing, shaping, or enriching an imagined world or setting.
-
B.
weaponDesigner
Indicates that one entity is the creator or designer of a weapon used or associated with another entity.
-
C.
builtDevice
Indicates that one entity constructed or assembled a device for or associated with another entity.
-
D.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
-
E.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:43 a.m.