Triple
T36648212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidaan |
E904766
|
entity |
| Predicate | coachDepicted |
P81506
|
FINISHED |
| Object | Syed Abdul Rahim |
—
|
NE NERFINISHED |
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: Syed Abdul Rahim | Statement: [Maidaan, coachDepicted, Syed Abdul Rahim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachDepicted Context triple: [Maidaan, coachDepicted, Syed Abdul Rahim]
-
A.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
B.
coachInvolved
Indicates that a coach participates in, influences, or is actively engaged in a particular event, activity, or interaction involving others.
-
C.
coachProduced
Indicates that a coach was responsible for developing, training, or otherwise producing the performance or outcome associated with an entity.
-
D.
featuredCoach
chosen
Indicates that a particular coach is highlighted or given special prominence within a specific context or collection.
-
E.
coachType
Indicates the specific category or role of a coach associated with an entity (e.g., head coach, assistant coach, position coach).
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.