Triple
T33404716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Lasso Experience |
E855406
|
entity |
| Predicate | characterTypeOfOperator |
P49696
|
FINISHED |
| Object | former child star |
—
|
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: former child star | Statement: [Star Lasso Experience, characterTypeOfOperator, former child star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterTypeOfOperator Context triple: [Star Lasso Experience, characterTypeOfOperator, former child star]
-
A.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
B.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
-
C.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
D.
employsCharacterType
Indicates that an entity makes use of or features a particular type or category of character in its content or structure.
-
E.
workCharacterType
chosen
Indicates that a work involves or features a character of a specified type or role.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:36 a.m.