Triple
T15195940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Shadow |
E363138
|
entity |
| Predicate | hasStageNameLanguage |
P21937
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Twin Shadow, hasStageNameLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageNameLanguage Context triple: [Twin Shadow, hasStageNameLanguage, English]
-
A.
hasStageNameVariant
Indicates that an entity has an alternative or variant form of its stage name.
-
B.
basedOnLanguageStage
Indicates that something is determined, classified, or derived according to a particular stage or level of language development or proficiency.
-
C.
hasFatherStageName
Indicates that an entity has a father whose commonly used or professional name is the specified stage name.
-
D.
hasNameInLocalLanguage
chosen
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
E.
hasMotherStageName
Indicates that an entity has a mother whose professional or stage name is specified by the related value.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067fcc788190abdc083d4eadeb36 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.