Triple
T18030528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Fit Together |
E431374
|
entity |
| Predicate | hasPerformerMemberType |
P121
|
FINISHED |
| Object | vocal 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: vocal group | Statement: [We Fit Together, hasPerformerMemberType, vocal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerMemberType Context triple: [We Fit Together, hasPerformerMemberType, vocal group]
-
A.
hasPerformerGroupType
Indicates that an entity is associated with a performer group of a specific type or category (e.g., band, choir, ensemble).
-
B.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasPerformerFamily
Indicates that an entity has a family member who performs or participates as a performer in relation to that entity.
-
D.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
E.
mainPerformerMemberOf
Indicates that the primary performer in an event or work is a member of a specified group, band, ensemble, or organization.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be35a70081909d24d36506d18131 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.