Triple
T5929695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Complex League |
E131903
|
entity |
| Predicate | rosterRestriction |
P55075
|
FINISHED |
| Object | primarily first-year professionals |
—
|
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: primarily first-year professionals | Statement: [Arizona Complex League, rosterRestriction, primarily first-year professionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterRestriction Context triple: [Arizona Complex League, rosterRestriction, primarily first-year professionals]
-
A.
rosterRequirement
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
B.
squadRestrictionForInvitedTeams
Indicates a constraint or rule that applies to the squad composition or size specifically for teams that have been invited.
-
C.
rankRestriction
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
-
D.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
E.
teamConstraint
chosen
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.