Triple
T35806705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old School |
E1035118
|
entity |
| Predicate | requiresTopRopeAccess |
P97397
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Old School, requiresTopRopeAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTopRopeAccess Context triple: [Old School, requiresTopRopeAccess, true]
-
A.
requiresTechnicalClimbing
chosen
Indicates that performing or traversing the subject (e.g., a route, path, or feature) necessitates the use of technical climbing skills, techniques, and/or specialized equipment.
-
B.
climbingAccess
Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
-
C.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
D.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
-
E.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 3, 2026, 4:06 p.m.