Triple
T32781532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R27 |
E838366
|
entity |
| Predicate | hasTrackGroup |
P104125
|
FINISHED |
| Object | Broad Street station tracks |
—
|
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: Broad Street station tracks | Statement: [R27, hasTrackGroup, Broad Street station tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackGroup Context triple: [R27, hasTrackGroup, Broad Street station tracks]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasTrackSection
chosen
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
-
C.
hasTrackControl
Indicates that one entity has authority or capability to manage, direct, or regulate the operation or behavior of another entity’s track or tracking process.
-
D.
hasTrackSelection
Indicates that an entity is associated with a specific choice or configuration among multiple available tracks (such as audio, video, or data streams).
-
E.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:14 a.m.