Triple
T32639017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Way |
E834428
|
entity |
| Predicate | hasMainSurfaceType |
P40183
|
FINISHED |
| Object | mixed road and 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: mixed road and trail | Statement: [French Way, hasMainSurfaceType, mixed road and trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSurfaceType Context triple: [French Way, hasMainSurfaceType, mixed road and trail]
-
A.
hasPrimarySurface
chosen
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasSurfacePreference
Indicates that an entity tends to favor or is best suited for interacting with a particular type of surface over others.
-
C.
hasSurfaceBlock
Indicates that one entity has another entity positioned on or forming its outermost surface layer.
-
D.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
E.
hasAlternativeSurface
Indicates that one entity serves as a different or substitute surface option for another entity.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:07 a.m.