Triple
T1461710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain West Conference |
E31525
|
entity |
| Predicate | hasAssociateMemberType |
P121
|
FINISHED |
| Object | associate members |
—
|
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: associate members | Statement: [Mountain West Conference, hasAssociateMemberType, associate members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociateMemberType Context triple: [Mountain West Conference, hasAssociateMemberType, associate members]
-
A.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
B.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
D.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
E.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59ecb60819082217b034e18381f |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.