Triple
T1208019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 30 Odd Foot of Grunts |
E25933
|
entity |
| Predicate | occupationOfMembers |
P14167
|
FINISHED |
| Object | musicians |
—
|
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: musicians | Statement: [30 Odd Foot of Grunts, occupationOfMembers, musicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationOfMembers Context triple: [30 Odd Foot of Grunts, occupationOfMembers, musicians]
-
A.
occupationOf
chosen
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
B.
representedOccupation
Indicates that one entity has served as an official or formal representative of another entity’s occupation or professional role.
-
C.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
-
D.
boardMembersRepresent
Indicates that designated board members act on behalf of, and in the interests of, a particular organization or group.
-
E.
memberHoldsOffice
Indicates that a member occupies or serves in a specific official position or office within an organization or governing body.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.