Triple
T25093641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victory City |
E628529
|
entity |
| Predicate | imaginaryEmpire |
P157633
|
FINISHED |
| Object | Bisnaga |
—
|
NE NERFINISHED |
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: Bisnaga | Statement: [Victory City, imaginaryEmpire, Bisnaga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imaginaryEmpire Context triple: [Victory City, imaginaryEmpire, Bisnaga]
-
A.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
B.
typeOfEmpire
Indicates the specific kind or classification of empire that an entity belongs to or represents.
-
C.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
D.
birthEmpire
Indicates that an entity was born within the territory or jurisdiction of a specified empire.
-
E.
governingEmpireAtConstruction
Indicates the empire that held governing authority over a place or structure at the time it was constructed.
- F. None of above. chosen
Provenance (4 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b691bc81908e0a286c32a902e8 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:24 a.m.