Triple
T8351887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway Twitty (stage surname component) |
E196580
|
entity |
| Predicate | usedAsCreditName |
P13305
|
FINISHED |
| Object | recordings by Conway Twitty |
—
|
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: recordings by Conway Twitty | Statement: [Conway Twitty (stage surname component), usedAsCreditName, recordings by Conway Twitty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCreditName Context triple: [Conway Twitty (stage surname component), usedAsCreditName, recordings by Conway Twitty]
-
A.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
B.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
D.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
E.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8019fb308190a3edc744bd473a5b |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.