Triple
T8544127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Distance Runaround |
E202277
|
entity |
| Predicate | recordedByNationality |
P83233
|
FINISHED |
| Object | English band |
—
|
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: English band | Statement: [Long Distance Runaround, recordedByNationality, English band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedByNationality Context triple: [Long Distance Runaround, recordedByNationality, English band]
-
A.
hasDirectorNationality
Indicates that the nationality of a director is associated with a given entity (such as a film, organization, or work).
-
B.
alsoRecordedBy
Indicates that the same work, event, or material has been additionally recorded by another recorder or recording entity.
-
C.
producerNationality
Indicates that a producer has a particular national affiliation or country of origin.
-
D.
recordCountry
Indicates that an entity (such as a record or event) is associated with or originates from a specific country.
-
E.
mainlyRecordedBy
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
- F. None of above. chosen
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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e381d4819084e230389a3ecb77 |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:18 p.m.