Triple
T24877602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfield horseshoe |
E622614
|
entity |
| Predicate | isUsuallyWalked |
P74037
|
FINISHED |
| Object | anticlockwise |
—
|
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: anticlockwise | Statement: [Fairfield horseshoe, isUsuallyWalked, anticlockwise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsuallyWalked Context triple: [Fairfield horseshoe, isUsuallyWalked, anticlockwise]
-
A.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
-
B.
usesCaninesFor
Indicates a relationship where an entity employs or relies on its canine teeth for a particular function or activity.
-
C.
walkingPolicy
Indicates the rules or guidelines that govern how walking is allowed, managed, or restricted in a given context.
-
D.
hasWalkingRouteType
chosen
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
E.
hasPrimaryGait
Indicates that one entity is the main or characteristic type of gait (manner of walking or locomotion) exhibited by 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:24 a.m.