Triple
T34904919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evan Alex |
E1006695
|
entity |
| Predicate | isChildPerformerIn |
P67683
|
FINISHED |
| Object | Hollywood films |
—
|
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: Hollywood films | Statement: [Evan Alex, isChildPerformerIn, Hollywood films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isChildPerformerIn Context triple: [Evan Alex, isChildPerformerIn, Hollywood films]
-
A.
childPerformer
chosen
Indicates a relationship where the subject is a performer who is a child, typically under a certain age, participating in a performance or production.
-
B.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
C.
performerInShow
Indicates that an entity participates as a performer in a particular show or performance.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
performedAsSingerIn
Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.