Triple
T28491520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnardo |
E720982
|
entity |
| Predicate | servesAtLocation |
P193998
|
FINISHED |
| Object | Elsinore Castle |
—
|
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: Elsinore Castle | Statement: [Barnardo, servesAtLocation, Elsinore Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAtLocation Context triple: [Barnardo, servesAtLocation, Elsinore Castle]
-
A.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
B.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
C.
mayServeAt
Indicates that one entity is permitted or authorized to perform service or duties at a specified location, organization, or context.
-
D.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
E.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: April 28, 2026, 3:01 a.m.