Triple
T25997574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJP |
E646526
|
entity |
| Predicate | identifiesStationType |
P27765
|
FINISHED |
| Object | passenger railway station |
—
|
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: passenger railway station | Statement: [TJP, identifiesStationType, passenger railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesStationType Context triple: [TJP, identifiesStationType, passenger railway station]
-
A.
identifiesPhysicalStation
Indicates that one entity specifies or designates the particular physical station associated with another entity.
-
B.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
C.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
D.
servesStationType
Indicates that an entity provides service to, or operates in connection with, a particular type or category of station.
-
E.
identifiesStationInDatabase
Indicates that an entity is recognized and matched as a specific station within a database system.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057012248190a486e723fdd2107e |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:58 a.m.