Triple
T3056525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From a Distance |
E60492
|
entity |
| Predicate | singleType |
P44817
|
FINISHED |
| Object | lead single |
—
|
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: lead single | Statement: [From a Distance, singleType, lead single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleType Context triple: [From a Distance, singleType, lead single]
-
A.
singleFrom
Indicates that one entity is derived as a single, distinct item from another source or collection.
-
B.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
C.
thirdSingle
Indicates that an entity is the third single (e.g., third single release) associated with another entity, typically in a sequence such as from an album or artist.
-
D.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
E.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf7ebd48190ad5748a18fa9a56a |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.