Triple
T35408979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popstars (UK TV series) |
E1023448
|
entity |
| Predicate | createdPopGroup |
P192981
|
FINISHED |
| Object | Hear'Say |
—
|
NE NERFINISHED |
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: Hear'Say | Statement: [Popstars (UK TV series), createdPopGroup, Hear'Say]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPopGroup Context triple: [Popstars (UK TV series), createdPopGroup, Hear'Say]
-
A.
broughtPopulationGroup
Indicates that one entity caused or facilitated the movement or arrival of a specific population group to another entity or location.
-
B.
controlsPopulationGroup
Indicates that one entity has authority, power, or mechanisms to direct, regulate, or dominate the behavior, movement, or conditions of a specific population group.
-
C.
createdByCharacterGroup
Indicates that something was created collectively by a specific group of characters acting together.
-
D.
creatorOfGroup
Indicates that one entity is the originator or founder responsible for creating a particular group.
-
E.
creationResult
chosen
Indicates that one entity is the outcome or product that comes into existence as a result of another entity’s act of creation.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.