Triple
T16271467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nant Cwm Colhuw |
E395008
|
entity |
| Predicate | toponymElement |
P96333
|
FINISHED |
| Object | Nant |
—
|
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: Nant | Statement: [Nant Cwm Colhuw, toponymElement, Nant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymElement Context triple: [Nant Cwm Colhuw, toponymElement, Nant]
-
A.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
B.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
C.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
D.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
E.
toponymyContainsElement
chosen
Indicates that a toponym (place name) includes a specific linguistic or semantic element as part of its composition.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e246099dd081908e268a1a0cf8a373 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.