Triple
T9887170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaq Diesel |
E180962
|
entity |
| Predicate | performerIs |
P20624
|
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: [Shaq Diesel, performerIs, professional basketball player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerIs Context triple: [Shaq Diesel, performerIs, professional basketball player]
-
A.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
B.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb457c8cc81909d211d5882228076 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.