Triple
T38543030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Saltdogs |
E924885
|
entity |
| Predicate | hasLeagueStatus |
P147701
|
FINISHED |
| Object | independent league |
—
|
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: independent league | Statement: [Lincoln Saltdogs, hasLeagueStatus, independent league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueStatus Context triple: [Lincoln Saltdogs, hasLeagueStatus, independent league]
-
A.
associatedLeagueStatus
Indicates that there exists a relationship specifying the league-related status or standing of an associated entity within a particular league context.
-
B.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
C.
parentLeagueStatus
Indicates the status or condition of a league in relation to its parent league or overarching league structure.
-
D.
traditionalLeagueStatus
Indicates whether an entity holds a historically established or customary status within a particular league or competitive organization.
-
E.
independentLeagueStatus
chosen
Indicates that an entity operates as an independent league, not formally affiliated with a larger governing or parent league system.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 3, 2026, 4:32 p.m.