Triple
T9375813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High and Dry |
E225642
|
entity |
| Predicate | trackNumberOnTheBends |
P7270
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [High and Dry, trackNumberOnTheBends, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnTheBends Context triple: [High and Dry, trackNumberOnTheBends, 3]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
tracksIndex
Indicates that one entity maintains or records the position, order, or index of another entity within a sequence or collection.
-
C.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
D.
trackName
Indicates the name or title assigned to a specific track (such as a song, audio piece, or route) in the relationship.
-
E.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50aa3d008190836d0fde840da7d2 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6c733881908aa3070830c2100b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:44 p.m.