Triple
T26352373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amersham station |
E662935
|
entity |
| Predicate | hasMainLineTracks |
P3492
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Amersham station, hasMainLineTracks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLineTracks Context triple: [Amersham station, hasMainLineTracks, yes]
-
A.
hasMainTrunkLine
chosen
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
-
B.
hasTwoTracks
Indicates that the subject possesses or is associated with exactly two distinct tracks or pathways.
-
C.
hasTailTracks
Indicates that an entity exhibits or leaves behind tail-shaped tracks or imprints as evidence of its movement or presence.
-
D.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
E.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 26, 2026, 10:46 p.m.