Triple
T9805761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Gulf Coast Eagles baseball |
E237948
|
entity |
| Predicate | hasProducedMLBPlayers |
P72299
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Florida Gulf Coast Eagles baseball, hasProducedMLBPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProducedMLBPlayers Context triple: [Florida Gulf Coast Eagles baseball, hasProducedMLBPlayers, true]
-
A.
hasProducedPlayersFor
Indicates that one entity has been the source or origin of players who go on to be associated with, or participate for, another entity.
-
B.
allowsMLBPlayers
Indicates that one entity grants permission or authorization for Major League Baseball players to participate in, access, or make use of another entity or activity.
-
C.
notableMLBAlumni
chosen
Indicates that the subject has alumni who went on to play Major League Baseball and are considered notable.
-
D.
hitsInMLB
Indicates the number of successful base hits a player has recorded in Major League Baseball games.
-
E.
playedBaseball
Indicates that an entity participated in playing the sport of baseball, typically as a player in a game or activity.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7b67748190ba16ce868f29d13e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.