Triple
T10984121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subashiri Trail |
E259582
|
entity |
| Predicate | crowdingLevel |
P18989
|
FINISHED |
| Object | less crowded than Yoshida Trail |
—
|
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: less crowded than Yoshida Trail | Statement: [Subashiri Trail, crowdingLevel, less crowded than Yoshida Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crowdingLevel Context triple: [Subashiri Trail, crowdingLevel, less crowded than Yoshida Trail]
-
A.
hasCrowdLevel
chosen
Indicates the degree or intensity of how crowded a place, event, or situation is.
-
B.
isLessCrowdedThan
Indicates that one place, event, or situation has fewer people present than another for comparison.
-
C.
relativeTrafficLevel
Indicates the comparative intensity or volume of traffic between two or more locations, routes, or time periods.
-
D.
trafficLevel
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
E.
populationConcentration
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ec55fc81909b2b15f2493dddc6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.