Triple
T32363246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos St. John Phillips |
E826920
|
entity |
| Predicate | hasStageNameStyle |
P153527
|
FINISHED |
| Object | all-caps stylization "SAINt JHN" |
—
|
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: all-caps stylization "SAINt JHN" | Statement: [Carlos St. John Phillips, hasStageNameStyle, all-caps stylization "SAINt JHN"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageNameStyle Context triple: [Carlos St. John Phillips, hasStageNameStyle, all-caps stylization "SAINt JHN"]
-
A.
hasStageNameVariant
Indicates that an entity has an alternative or variant form of its stage name.
-
B.
usesStageNameFormat
chosen
Indicates that an entity’s stage name follows or conforms to a particular naming format or pattern.
-
C.
hasFatherStageName
Indicates that an entity has a father whose commonly used or professional name is the specified stage name.
-
D.
hasStyleName
Indicates that an entity is associated with a particular style through a specific style name.
-
E.
useOfStageName
Indicates that an entity performs or is known publicly under a stage name rather than their legal or original name.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 12:50 a.m.