Triple
T1114834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coming Home |
E11073
|
entity |
| Predicate | hasReleaseContext |
P19968
|
FINISHED |
| Object | album track rather than 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: album track rather than lead single | Statement: [Coming Home, hasReleaseContext, album track rather than lead single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseContext Context triple: [Coming Home, hasReleaseContext, album track rather than lead single]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
C.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
D.
releaseContext
Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
-
E.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.