Triple
T36363235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanygrisiau |
E895550
|
entity |
| Predicate | transportTypeNearby |
P1379
|
FINISHED |
| Object | narrow-gauge railway |
—
|
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: narrow-gauge railway | Statement: [Tanygrisiau, transportTypeNearby, narrow-gauge railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportTypeNearby Context triple: [Tanygrisiau, transportTypeNearby, narrow-gauge railway]
-
A.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
B.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transportSubmode
Indicates a more specific categorization of a general transport mode, defining the particular sub-type or variant of transportation being used.
-
D.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
E.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:10 p.m.