Triple
T33510037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born to Run |
E858214
|
entity |
| Predicate | firstReleasedAsSingleInTerritory |
P67545
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [Born to Run, firstReleasedAsSingleInTerritory, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleasedAsSingleInTerritory Context triple: [Born to Run, firstReleasedAsSingleInTerritory, United States]
-
A.
firstReleasedAsSingleBy
Indicates that a musical work was first released in the form of a single by a specific artist or performer.
-
B.
releasedAsSingleInTerritory
chosen
Indicates that a work (such as a song or recording) was issued as a single in a specific geographic territory or market.
-
C.
releasedAsSingleIn
Indicates that a musical work or track was issued as a standalone single in a specific year or time period.
-
D.
releasedAsSingleFor
Indicates that a particular track or song was issued as a standalone single specifically to promote or represent a given album, project, or release.
-
E.
originallyReleasedAsSingle
Indicates that a work (such as a song) was first issued to the public in the form of a single release.
- F. None of above.
Provenance (4 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a359592e6088190b0a8b3e00604b1ed |
completed | June 19, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.