Triple
T34607316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduard (former municipality) |
E888628
|
entity |
| Predicate | locatedInFormerAbbeyTerritory |
P205482
|
FINISHED |
| Object | Aduard |
E255824
|
NE 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: Aduard | Statement: [Aduard (former municipality), locatedInFormerAbbeyTerritory, Aduard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFormerAbbeyTerritory Context triple: [Aduard (former municipality), locatedInFormerAbbeyTerritory, Aduard]
-
A.
abbeyLocation
Indicates the geographical place where an abbey is situated or located.
-
B.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
C.
locatedInFormerNamePlace
Indicates that an entity is located in a place that is referred to by its former or historical name rather than its current name.
-
D.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
E.
abbeyOverlooks
Indicates that an abbey is situated so that it has a clear, elevated, or commanding view over a particular place or landscape.
- F. None of above. chosen
Provenance (5 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376619fc048190b8886a5887c7b793 |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:03 a.m.