Triple
T6776389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mules |
E155165
|
entity |
| Predicate | hasNotableProgramIn |
P10900
|
FINISHED |
| Object | men's basketball |
—
|
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: men's basketball | Statement: [Mules, hasNotableProgramIn, men's basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProgramIn Context triple: [Mules, hasNotableProgramIn, men's basketball]
-
A.
hasPublicProgram
Indicates that an entity offers or participates in a program or initiative that is accessible to the general public.
-
B.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
C.
hasStrongProgramIn
Indicates that an institution or organization offers a particularly high-quality or well-regarded program in a specified field or area.
-
D.
notableProgramInvolvement
chosen
Indicates that an entity has a significant or distinguished role or participation in a particular program.
-
E.
hasEducationalProgram
Indicates that an entity offers, runs, or is associated with a specific educational program.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24f77c88190be21cf4ef132aa31 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.