Triple
T33576288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Arrival |
E860036
|
entity |
| Predicate | isByGroupType |
P124500
|
FINISHED |
| Object | teen pop group |
—
|
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: teen pop group | Statement: [New Arrival, isByGroupType, teen pop group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isByGroupType Context triple: [New Arrival, isByGroupType, teen pop group]
-
A.
isGroupUnder
Indicates that one group is organizationally or hierarchically subordinate to, or contained within, another group.
-
B.
isBySupergroup
Indicates that something (such as a work, event, or item) is created, performed, or produced by a supergroup, i.e., a group formed from members of other established groups.
-
C.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
D.
appliedToGroupType
Indicates that something (such as a rule, setting, or action) is applied specifically to a particular type or category of group rather than to individual members.
-
E.
identifiesGroup
chosen
Indicates that one entity serves to recognize, label, or distinguish another entity as belonging to a particular group or category.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74c503c8190b462600d76696b2f |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.