Triple
T22326976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trikken |
E551925
|
entity |
| Predicate | hasTypeOfTrack |
P3832
|
FINISHED |
| Object | street-running track |
—
|
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: street-running track | Statement: [Trikken, hasTypeOfTrack, street-running track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTrack Context triple: [Trikken, hasTypeOfTrack, street-running track]
-
A.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
hasTrackFeatures
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
E.
hasTrackSection
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157693460819087c165481eb9e128 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.