Triple
T5704285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotary Algonquin Regiment Fitness Trail |
E125745
|
entity |
| Predicate | hasAccessCost |
P47431
|
FINISHED |
| Object | free of charge |
—
|
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: free of charge | Statement: [Rotary Algonquin Regiment Fitness Trail, hasAccessCost, free of charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessCost Context triple: [Rotary Algonquin Regiment Fitness Trail, hasAccessCost, free of charge]
-
A.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
hasAccessConstraint
chosen
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
-
E.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024585d14819098ec34fd5a858836 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.