Triple
T33539080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-American Conference wrestling programs |
E859020
|
entity |
| Predicate | teamLimitPerLineup |
P3315
|
FINISHED |
| Object | one wrestler per weight class |
—
|
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: one wrestler per weight class | Statement: [Mid-American Conference wrestling programs, teamLimitPerLineup, one wrestler per weight class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLimitPerLineup Context triple: [Mid-American Conference wrestling programs, teamLimitPerLineup, one wrestler per weight class]
-
A.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
B.
teamRosterLimit
chosen
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
C.
lineoutPlayersPerTeam
Indicates the number of players assigned to participate in a lineout for each team.
-
D.
teamLimitPerAssociation
Indicates the maximum number of teams that can be associated with a single association or grouping.
-
E.
teamLimitInRecentEditions
Indicates a constraint on the number of teams allowed to participate in the most recent editions of a competition or event.
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.