Triple
T21729053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money Ball |
E536351
|
entity |
| Predicate | associatedPerformerOccupation |
P50979
|
FINISHED |
| Object | professional basketball player |
—
|
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: professional basketball player | Statement: [Money Ball, associatedPerformerOccupation, professional basketball player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPerformerOccupation Context triple: [Money Ball, associatedPerformerOccupation, professional basketball player]
-
A.
hasMainPerformerOccupation
chosen
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
B.
artistOccupation
Indicates the professional role or job that an artist holds or performs.
-
C.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
D.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
E.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd04c9648190922e8fa7c74ac1b5 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.