Triple
T32113615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guard of the Citadel |
E820179
|
entity |
| Predicate | guardedPlace |
P64110
|
FINISHED |
| Object | Court of the Fountain |
—
|
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: Court of the Fountain | Statement: [Guard of the Citadel, guardedPlace, Court of the Fountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedPlace Context triple: [Guard of the Citadel, guardedPlace, Court of the Fountain]
-
A.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
B.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
C.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
-
D.
notableLocationGuarded
chosen
Indicates that a notable or significant location is being actively protected or guarded by an entity.
-
E.
hidingPlace
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:27 a.m.