Triple
T2102582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pwllheli (via Cambrian Coast) |
E37122
|
entity |
| Predicate | primaryRailUse |
P35841
|
FINISHED |
| Object | tourism |
—
|
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: tourism | Statement: [Pwllheli (via Cambrian Coast), primaryRailUse, tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRailUse Context triple: [Pwllheli (via Cambrian Coast), primaryRailUse, tourism]
-
A.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
B.
formerRailUse
Indicates that an entity previously served a particular railway-related function or purpose, but no longer does so.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
E.
railroadMet
Indicates that two or more railroads encountered or connected with each other at a specific place or time.
- F. None of above. chosen
Provenance (4 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabe1e9081908ea66c5406e2f1d9 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb9ce3ff08190a9501f8bb821c01c |
completed | March 7, 2026, 5:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.