Triple
T35448115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isca Dumnoniorum |
E1024541
|
entity |
| Predicate | nearbyModernBuilding |
P44972
|
FINISHED |
| Object | Exeter Cathedral precinct |
—
|
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: Exeter Cathedral precinct | Statement: [Isca Dumnoniorum, nearbyModernBuilding, Exeter Cathedral precinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyModernBuilding Context triple: [Isca Dumnoniorum, nearbyModernBuilding, Exeter Cathedral precinct]
-
A.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
B.
hasMainBuildingNear
chosen
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
C.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
D.
nearModernAvenue
Indicates that one entity is located close to or in the vicinity of a modern avenue.
-
E.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:04 p.m.