Triple
T19330478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deer statue of Elafina |
E483474
|
entity |
| Predicate | standsAt |
P135444
|
FINISHED |
| Object | entrance of Mandraki Harbor |
—
|
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: entrance of Mandraki Harbor | Statement: [deer statue of Elafina, standsAt, entrance of Mandraki Harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standsAt Context triple: [deer statue of Elafina, standsAt, entrance of Mandraki Harbor]
-
A.
hasStandsOn
Indicates that one entity is physically supported by and in contact with the upper surface of another entity.
-
B.
stoodAtStudAt
Indicates that one entity was positioned or located at a particular stud (e.g., structural post or support point).
-
C.
stands
Indicates that an entity is in an upright position, typically supported by its feet or base, rather than sitting, lying, or moving.
-
D.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
E.
standingAtStud
Indicates that one entity is standing at or positioned next to a specific stud or stud-like structural element.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e616412bcc81909bb34d3cf5363129 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:33 p.m.