Triple
T3413562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shikoku 88-temple pilgrimage |
E71953
|
entity |
| Predicate | typicalTravelMode |
P1379
|
FINISHED |
| Object | on foot |
—
|
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: on foot | Statement: [Shikoku 88-temple pilgrimage, typicalTravelMode, on foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTravelMode Context triple: [Shikoku 88-temple pilgrimage, typicalTravelMode, on foot]
-
A.
publicTransitMode
Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
-
B.
transportModeFamily
Indicates the general category or family of transportation mode to which a specific transport mode belongs (e.g., road, rail, air, water).
-
C.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
travelTimeTypical
Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb927e8d081908a5ab283da93beb2 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.