Triple
T18557565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASCAP Nashville office |
E453543
|
entity |
| Predicate | servesRoleFor |
P11687
|
FINISHED |
| Object | ASCAP songwriter members |
—
|
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: ASCAP songwriter members | Statement: [ASCAP Nashville office, servesRoleFor, ASCAP songwriter members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRoleFor Context triple: [ASCAP Nashville office, servesRoleFor, ASCAP songwriter members]
-
A.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
B.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
acknowledgesRoleOf
Indicates that one entity explicitly recognizes and accepts the position, function, or authority that another entity holds.
-
E.
servesMember
Indicates that one entity provides services or assistance to another entity that is considered its member.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53808028c8190825630525d84a29b |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:40 a.m.