Triple
T29238490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This Strange Engine |
E741253
|
entity |
| Predicate | longestTrackDuration |
P165539
|
FINISHED |
| Object | approximately 15 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 15 minutes | Statement: [This Strange Engine, longestTrackDuration, approximately 15 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestTrackDuration Context triple: [This Strange Engine, longestTrackDuration, approximately 15 minutes]
-
A.
longestTrack
Indicates that the related track is the one with the greatest duration or length among a given set of tracks.
-
B.
longestDurationAt
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
C.
playingTimeMinutesMaximum
chosen
Indicates the maximum allowed or recorded duration, in minutes, for which something can be played.
-
D.
lengthInMinutes
Indicates the duration of something expressed as a number of minutes.
-
E.
notableTrackLength
Indicates that there is a track whose duration is considered significant or noteworthy in the context of the subject.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66466747481909182bd6cf85d8eff |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:30 p.m.