Triple
T36814073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberconwy Abbey |
E909674
|
entity |
| Predicate | currentRemainsLocatedIn |
P103021
|
FINISHED |
| Object | Conwy |
—
|
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: Conwy | Statement: [Aberconwy Abbey, currentRemainsLocatedIn, Conwy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentRemainsLocatedIn Context triple: [Aberconwy Abbey, currentRemainsLocatedIn, Conwy]
-
A.
remainsLocation
chosen
Indicates that the physical remains of an entity are located or kept at a specified place.
-
B.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
C.
someElementsNowLocatedIn
Indicates that at least one element of a previously defined set is currently located within a specified place or region.
-
D.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
E.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.