Triple
T19380334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ystalyfera community |
E484788
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Gurnos |
—
|
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: Gurnos | Statement: [Ystalyfera community, contains, Gurnos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gurnos Context triple: [Ystalyfera community, contains, Gurnos]
-
A.
Gurnos
chosen
Gurnos is a residential area in South Wales located near the town of Ystradgynlais.
-
B.
Alvarus
Alvarus is a Latinized variant of the given name Alvar, historically used in medieval and ecclesiastical contexts.
-
C.
Balranald
Balranald is a rural town in the western Riverina region of New South Wales, Australia, situated on the banks of the Murrumbidgee River.
-
D.
Sonnius
Sonnius is a Dutch-language surname most notably associated with Franciscus Sonnius, a 16th-century Catholic theologian and bishop from the Low Countries.
-
E.
Togodumnus
Togodumnus was a 1st-century AD British tribal leader, likely a king of the Catuvellauni, who opposed the Roman invasion of Britain under Emperor Claudius.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5fc1c48190b9d8fd5f5c10ec2c |
completed | April 20, 2026, 12:21 p.m. |
Created at: April 10, 2026, 1:35 p.m.