Triple
T35207270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Citadel |
E1016569
|
entity |
| Predicate | locationRole |
P69710
|
FINISHED |
| Object | seat of command |
—
|
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: seat of command | Statement: [the Citadel, locationRole, seat of command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRole Context triple: [the Citadel, locationRole, seat of command]
-
A.
addressRole
Indicates the specific function or capacity an entity has in relation to a given address (e.g., owner, recipient, billing contact).
-
B.
hasLocationRole
chosen
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.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
D.
addressesRole
Indicates that one entity directs communication, content, or action specifically toward another entity in its capacity or function as a particular role.
-
E.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.