Triple
T34483394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etta James discography |
E885248
|
entity |
| Predicate | notableSingleIncluded |
P65828
|
FINISHED |
| Object | At Last |
E253142
|
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: At Last | Statement: [Etta James discography, notableSingleIncluded, At Last]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSingleIncluded Context triple: [Etta James discography, notableSingleIncluded, At Last]
-
A.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
B.
notableCollectionIncludes
chosen
Indicates that a notable or significant collection contains or features the specified item as one of its components.
-
C.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
D.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729d5abf88190bc72af8b0fb71590 |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.