Triple
T16217193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacksonville Jumbo Shrimp |
E393623
|
entity |
| Predicate | beganPlayAsJumboShrimp |
P122210
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Jacksonville Jumbo Shrimp, beganPlayAsJumboShrimp, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPlayAsJumboShrimp Context triple: [Jacksonville Jumbo Shrimp, beganPlayAsJumboShrimp, 2017]
-
A.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
B.
startSea
Indicates that an entity begins its journey, activity, or existence at sea or from a maritime location.
-
C.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
D.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
E.
aimsToStartPlay
Indicates that an entity intends or attempts to initiate a play or performance activity involving another entity.
- F. None of above. chosen
Provenance (4 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f76f748190831d230d32c18611 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.