Triple
T33659141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Kalvan of Otherwhen |
E862302
|
entity |
| Predicate | hasFictionalPolity |
P82060
|
FINISHED |
| Object | Kingdom of Hostigos |
—
|
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: Kingdom of Hostigos | Statement: [Lord Kalvan of Otherwhen, hasFictionalPolity, Kingdom of Hostigos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalPolity Context triple: [Lord Kalvan of Otherwhen, hasFictionalPolity, Kingdom of Hostigos]
-
A.
hasFictionalEstablishmentType
Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
-
B.
polityInFictionalWorld
chosen
Indicates that a political entity exists within, or is part of, a fictional world or universe.
-
C.
hasFictionalWorldType
Indicates that an entity is associated with, set in, or characterized by a particular type or category of fictional world.
-
D.
hasFictionalUniverseStatus
Indicates that an entity holds a particular status or classification within a fictional universe or continuity.
-
E.
hasFictionalInhabitants
Indicates that a place or setting is inhabited by fictional or imaginary beings.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 1:42 a.m.