Triple
T4742662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radziejowa |
E105281
|
entity |
| Predicate | isAccessibleByMarkedTrails |
P47567
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Radziejowa, isAccessibleByMarkedTrails, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessibleByMarkedTrails Context triple: [Radziejowa, isAccessibleByMarkedTrails, yes]
-
A.
trailsMarkedBy
chosen
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
B.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
C.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
D.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
E.
hasTrailConnection
Indicates that one location is connected to another by a traversable trail or path.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.