Triple
T38034383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianhead Mountain ski area |
E949007
|
entity |
| Predicate | primaryTransportAccess |
P147666
|
FINISHED |
| Object | automobile |
—
|
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: automobile | Statement: [Indianhead Mountain ski area, primaryTransportAccess, automobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTransportAccess Context triple: [Indianhead Mountain ski area, primaryTransportAccess, automobile]
-
A.
primaryTransports
Indicates that one entity serves as the main means or method of transporting or conveying another entity.
-
B.
transportAccessType
chosen
Indicates the type or mode of transportation access available or used in a given context.
-
C.
primaryTransportFunction
Indicates the main mode or role by which something serves to move people, goods, or information from one place to another.
-
D.
transportAccessBy
Indicates that one entity has access to or is served by a particular mode or means of transportation provided or enabled by another entity.
-
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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.