Triple
T29663960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brother Where You Bound |
E750479
|
entity |
| Predicate | titleTrackLength |
P51781
|
FINISHED |
| Object | approximately 16 minutes |
—
|
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: approximately 16 minutes | Statement: [Brother Where You Bound, titleTrackLength, approximately 16 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleTrackLength Context triple: [Brother Where You Bound, titleTrackLength, approximately 16 minutes]
-
A.
notableTrackLength
Indicates that there is a track whose duration is considered significant or noteworthy in the context of the subject.
-
B.
longestTrack
Indicates that the related track is the one with the greatest duration or length among a given set of tracks.
-
C.
lapLengthOfTrack
Indicates the distance or length of a single lap around a track.
-
D.
lengthInMinutes
chosen
Indicates the duration of something expressed as a number of minutes.
-
E.
trackName
Indicates the name or title assigned to a specific track (such as a song, audio piece, or route) in the relationship.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 7 p.m.