Triple
T21957466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissaka-juku |
E542228
|
entity |
| Predicate | travelModeServed |
P133438
|
FINISHED |
| Object | foot traffic |
—
|
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: foot traffic | Statement: [Nissaka-juku, travelModeServed, foot traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelModeServed Context triple: [Nissaka-juku, travelModeServed, foot traffic]
-
A.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
modeOfService
Indicates the manner, method, or channel through which a service is delivered or provided.
-
D.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
E.
servedByTransportation
chosen
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244108948190a08e6966e55c4acd |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.