Triple
T4562587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neath North |
E121828
|
entity |
| Predicate | withinSettlement |
P55544
|
FINISHED |
| Object | town of Neath |
—
|
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: town of Neath | Statement: [Neath North, withinSettlement, town of Neath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinSettlement Context triple: [Neath North, withinSettlement, town of Neath]
-
A.
isSettlementOf
chosen
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
B.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
C.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
D.
settlementTerm
Indicates the agreed conditions, timing, and method by which an obligation, transaction, or dispute is settled between parties.
-
E.
enclosedSettlement
Indicates that one settlement is physically surrounded or contained within the boundaries of another settlement or enclosing structure.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd582f21648190b49284eb61b618c9 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.