Triple
T1441138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain West Conference men's basketball |
E31073
|
entity |
| Predicate | amateurOrProfessional |
P7462
|
FINISHED |
| Object | amateur |
—
|
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: amateur | Statement: [Mountain West Conference men's basketball, amateurOrProfessional, amateur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amateurOrProfessional Context triple: [Mountain West Conference men's basketball, amateurOrProfessional, amateur]
-
A.
isAmateur
chosen
Indicates that an entity engages in an activity or field on a non-professional, typically unpaid or hobbyist basis.
-
B.
semiProfessionalTiers
Indicates a relationship in which entities are organized or classified into tiers that represent semi-professional levels or statuses.
-
C.
isPro
Indicates that an entity is a professional or expert in a particular field, activity, or domain.
-
D.
amateurRequirement
Indicates that an entity must be an amateur or meet amateur-status conditions in order for a related activity, role, or classification to apply.
-
E.
historicallyAmateurUntil
Indicates that an entity was considered amateur, rather than professional, up to a specified point in time.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.