Triple
T27454444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudlersville, Maryland |
E692545
|
entity |
| Predicate | hasSportsMonument |
P75587
|
FINISHED |
| Object | Jimmie Foxx statue |
—
|
NE NERFINISHED |
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: Jimmie Foxx statue | Statement: [Sudlersville, Maryland, hasSportsMonument, Jimmie Foxx statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsMonument Context triple: [Sudlersville, Maryland, hasSportsMonument, Jimmie Foxx statue]
-
A.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
B.
hasSportsHallOfFame
Indicates that an entity possesses or hosts a designated Sports Hall of Fame associated with it.
-
C.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
D.
significantVenueFor
Indicates that a venue plays an important or notable role in relation to a particular entity, event, or activity.
-
E.
hasCommemorativeStructure
chosen
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 12:48 p.m.