Triple
T31912464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Show Jones |
E814723
|
entity |
| Predicate | isStageRelatedName |
P3889
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [No Show Jones, isStageRelatedName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStageRelatedName Context triple: [No Show Jones, isStageRelatedName, true]
-
A.
isRelatedName
chosen
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
B.
hasStageNameVariant
Indicates that an entity has an alternative or variant form of its stage name.
-
C.
associatedWithStageName
Indicates that an entity is connected to or known by a particular stage name used as an alternate professional identity.
-
D.
hasFatherStageName
Indicates that an entity has a father whose commonly used or professional name is the specified stage name.
-
E.
usesStageNameFormat
Indicates that an entity’s stage name follows or conforms to a particular naming format or pattern.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:01 a.m.