Triple
T13288618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell Corner |
E316505
|
entity |
| Predicate | trackSectionType |
P104125
|
FINISHED |
| Object | low-speed corner |
—
|
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: low-speed corner | Statement: [Hell Corner, trackSectionType, low-speed corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackSectionType Context triple: [Hell Corner, trackSectionType, low-speed corner]
-
A.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
B.
tracksSector
Indicates that one entity monitors, follows, or keeps records of the status or performance of a particular sector.
-
C.
hasTrackSection
chosen
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
-
D.
stratotypeSection
Indicates the reference rock section formally designated as the standard or type example for a particular stratigraphic unit or boundary.
-
E.
trackRole
Indicates that an entity holds or performs a specific role within the context of a particular track or sequence of activities.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.