Triple
T33322516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garnedd Uchaf |
E853175
|
entity |
| Predicate | liesInRangeBetween |
P1262
|
FINISHED |
| Object | Foel-fras and Carnedd Llewelyn |
—
|
LITERAL 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: Foel-fras and Carnedd Llewelyn | Statement: [Garnedd Uchaf, liesInRangeBetween, Foel-fras and Carnedd Llewelyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesInRangeBetween Context triple: [Garnedd Uchaf, liesInRangeBetween, Foel-fras and Carnedd Llewelyn]
-
A.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
C.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
-
D.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
E.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.