Triple
T35459669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Citadel of the Lich |
E1024878
|
entity |
| Predicate | isLocationType |
P134880
|
FINISHED |
| Object | citadel |
—
|
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: citadel | Statement: [The Citadel of the Lich, isLocationType, citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocationType Context triple: [The Citadel of the Lich, isLocationType, citadel]
-
A.
subjectLocationType
chosen
Indicates the type or category of location associated with the subject in the relationship.
-
B.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
C.
currentLocationType
Indicates the type or category of place where an entity is currently located.
-
D.
settingLocationType
Indicates the type or category of location in which an event, action, or situation takes place.
-
E.
hasPhysicalLocationType
Indicates that an entity is associated with a specific kind or category of physical location (e.g., building type, facility type, or place type).
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:04 p.m.