Triple
T21715820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 国府津駅 |
E536025
|
entity |
| Predicate | 駅舎構造 |
P27765
|
FINISHED |
| Object | 橋上駅舎 |
—
|
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: 橋上駅舎 | Statement: [国府津駅, 駅舎構造, 橋上駅舎]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 駅舎構造 Context triple: [国府津駅, 駅舎構造, 橋上駅舎]
-
A.
formerRailwayStation
Indicates that a location previously functioned as a railway station but is no longer in active railway service.
-
B.
railwayStationStyle
Indicates that one entity is designed, built, or decorated in the architectural style characteristic of a particular railway station.
-
C.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
D.
railwayStationInside
Indicates that a railway station is located within the boundaries or interior area of another place or structure.
-
E.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53761b48190954a46e8155a84f0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.