Triple
T14436275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holly Springs Salamanders |
E357969
|
entity |
| Predicate | hasLeagueFormat |
P21421
|
FINISHED |
| Object | wood-bat collegiate summer 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: wood-bat collegiate summer league | Statement: [Holly Springs Salamanders, hasLeagueFormat, wood-bat collegiate summer league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueFormat Context triple: [Holly Springs Salamanders, hasLeagueFormat, wood-bat collegiate summer league]
-
A.
usesLeagueAbbreviationFormat
Indicates that something follows or applies the abbreviation format convention used by a particular league.
-
B.
supportsLeagueType
Indicates that one entity is compatible with, or designed to work with, a particular type or category of league.
-
C.
isPartOfLeague
chosen
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
D.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
E.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.