Triple
T13962648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grześ |
E335834
|
entity |
| Predicate | hasTrailMarkingColor |
P14031
|
FINISHED |
| Object | yellow (from Chochołowska Valley) |
—
|
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: yellow (from Chochołowska Valley) | Statement: [Grześ, hasTrailMarkingColor, yellow (from Chochołowska Valley)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailMarkingColor Context triple: [Grześ, hasTrailMarkingColor, yellow (from Chochołowska Valley)]
-
A.
colorOfTrailMarkings
chosen
Indicates the relationship specifying what color the trail’s markings are.
-
B.
trailsMarkedBy
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
C.
trackColor
Indicates the color associated with a given track in a context such as audio, video, or data sequencing.
-
D.
hasTrailFeature
Indicates that a trail possesses or is characterized by a specific feature or attribute.
-
E.
hasRouteColorStandard
Indicates that a route is associated with a standardized color designation used for identification or classification.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:18 p.m.