Triple
T28813266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 富山市 |
E727572
|
entity |
| Predicate | 公共交通 |
P151823
|
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.
publicTransportation
chosen
Indicates that an entity provides, uses, or is associated with shared, publicly accessible transportation services (such as buses, trains, or subways) rather than private transport.
-
B.
publicTransportNetworkType
Indicates the type or category of public transportation network associated with or used by an entity.
-
C.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
D.
transportDevelopment
Indicates the development or improvement of transportation systems, infrastructure, or services connecting places or entities.
-
E.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.