Triple
T33281323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier League |
E852050
|
entity |
| Predicate | hasRosterSizeRule |
P21198
|
FINISHED |
| Object | limits number of veteran players per team |
—
|
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: limits number of veteran players per team | Statement: [Frontier League, hasRosterSizeRule, limits number of veteran players per team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRosterSizeRule Context triple: [Frontier League, hasRosterSizeRule, limits number of veteran players per team]
-
A.
hasRosterSizeCategory
Indicates the classification of an entity based on the size of its roster or group of members.
-
B.
hasMaximumNumberOfMembers
chosen
Indicates that there is an upper limit on how many members can be associated with a given entity.
-
C.
hasRosterStatus
Indicates the current membership or availability status of an entity within a defined roster or lineup.
-
D.
hasNumberOfRules
Indicates the specific count of rules associated with or applicable to an entity.
-
E.
rosterSize
Indicates the total number of individuals included on a given roster.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:32 a.m.