Triple
T37678856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle of Mey |
E938168
|
entity |
| Predicate | nearbyFacilityOperator |
P196388
|
FINISHED |
| Object | The Queen Elizabeth Castle of Mey Trust |
—
|
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: The Queen Elizabeth Castle of Mey Trust | Statement: [Castle of Mey, nearbyFacilityOperator, The Queen Elizabeth Castle of Mey Trust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyFacilityOperator Context triple: [Castle of Mey, nearbyFacilityOperator, The Queen Elizabeth Castle of Mey Trust]
-
A.
nearbyFacilityType
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
B.
operatesNear
chosen
Indicates that one entity performs its activities or functions in close physical proximity to another entity.
-
C.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
D.
operatedFacilityNear
Indicates that an entity operated a facility located in close geographic proximity to another specified entity or place.
-
E.
formerFacilityNearby
Indicates that an entity was previously located in a facility that was situated close to another specified entity or place.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 3, 2026, 4:18 p.m.