Triple
T24044699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guild Wheel cycle route |
E595484
|
entity |
| Predicate | hasLoopAround |
P36766
|
FINISHED |
| Object | Preston urban area |
—
|
NE NERFINISHED |
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: Preston urban area | Statement: [Guild Wheel cycle route, hasLoopAround, Preston urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopAround Context triple: [Guild Wheel cycle route, hasLoopAround, Preston urban area]
-
A.
hasLoopMode
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
-
B.
hasLoopOption
Indicates that an entity provides or supports an option to repeat or loop an associated process, action, or sequence.
-
C.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
D.
isLoop
chosen
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
E.
hasLoopConfiguration
Indicates that an entity is associated with a specific loop setup or arrangement that defines how a loop operates or is structured.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8dc8f708190ac6257e65c37bde7 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:11 p.m.