Triple
T33539085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-American Conference wrestling programs |
E859020
|
entity |
| Predicate | includeAssociateMembers |
P10953
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mid-American Conference wrestling programs, includeAssociateMembers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeAssociateMembers Context triple: [Mid-American Conference wrestling programs, includeAssociateMembers, yes]
-
A.
hasAssociateMember
chosen
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
B.
includeMember
Indicates that one entity contains or has another entity as a member or part of its composition.
-
C.
numberOfAssociateMembers
Indicates the total count of associate members linked to a given entity.
-
D.
includedMembersOf
Indicates that certain members or elements are contained within, or form part of, a specified group or collection.
-
E.
includedPlannedMember
Indicates that an entity has been designated or scheduled to be part of a group, set, or collection as a planned member.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
Created at: May 1, 2026, 1:39 a.m.