Triple
T18905032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochfirstschanze |
E462437
|
entity |
| Predicate | hasOutrun |
P133736
|
FINISHED |
| Object | outrun area |
—
|
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: outrun area | Statement: [Hochfirstschanze, hasOutrun, outrun area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutrun Context triple: [Hochfirstschanze, hasOutrun, outrun area]
-
A.
canOutrun
Indicates that one entity is able to run faster than another and thus surpass or escape it in a running context.
-
B.
designedToOutrun
Indicates that one entity was intentionally created or engineered with the capability to move faster than another entity.
-
C.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
-
D.
hasRun
Indicates that an entity has performed or completed a running activity or event at least once in the past.
-
E.
hasWalkedRunwayFor
Indicates that one entity has modeled or appeared on the fashion runway in a show organized by another entity.
- F. None of above. chosen
Provenance (4 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52c121c8190a2057b99c723694b |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4afa745c081908da20a51ebc147b4 |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 11:58 a.m.