Triple
T34922665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stray Dolls |
E1007188
|
entity |
| Predicate | featuresProtagonistFrom |
P21469
|
FINISHED |
| Object | South Asia |
E6055
|
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: South Asia | Statement: [Stray Dolls, featuresProtagonistFrom, South Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProtagonistFrom Context triple: [Stray Dolls, featuresProtagonistFrom, South Asia]
-
A.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
B.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
D.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
E.
featuresReturningCharacterFrom
Indicates that a work includes the reappearance of a character who previously appeared in the referenced source work.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8b318f481909e01ec8d09465cc0 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.