Triple
T35807186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phenom |
E1035130
|
entity |
| Predicate | hasMatchTypeSpecialty |
—
|
GENERATED |
| Object | Casket Match |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchTypeSpecialty Context triple: [The Phenom, hasMatchTypeSpecialty, Casket Match]
-
A.
matchTypeSpecialty
chosen
Indicates that two entities are related through a specific type of match based on a particular specialty or area of expertise.
-
B.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
C.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
D.
hasInstrumentSpecialty
Indicates that an entity (typically a person or professional) specializes in or is particularly skilled with a specific instrument.
-
E.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
- F. None of above.
Provenance (1 batch)
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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.