Triple
T34006986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Tall Sally (The Beatles EP) |
E871991
|
entity |
| Predicate | trackOnSideA |
P25310
|
FINISHED |
| Object | Long Tall Sally |
—
|
NE NERFINISHED |
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: Long Tall Sally | Statement: [Long Tall Sally (The Beatles EP), trackOnSideA, Long Tall Sally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackOnSideA Context triple: [Long Tall Sally (The Beatles EP), trackOnSideA, Long Tall Sally]
-
A.
side1Track
Indicates that an entity is associated with or belongs to the first side or track in a two-sided or multi-track configuration.
-
B.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
C.
onAlbumSide
chosen
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
-
D.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
E.
focusesOnSide
Indicates that an action, attention, or analysis is directed specifically toward one particular side or aspect of something.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:50 a.m.