Triple
T38509992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baby Bombers |
E921876
|
entity |
| Predicate | locationOfHomeVenue |
P51872
|
FINISHED |
| Object | St. George, Staten Island |
E234452
|
NE 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: St. George, Staten Island | Statement: [Baby Bombers, locationOfHomeVenue, St. George, Staten Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfHomeVenue Context triple: [Baby Bombers, locationOfHomeVenue, St. George, Staten Island]
-
A.
earlyHomeVenueFor
Indicates that one entity served as the primary home venue for another entity during an early or initial period of its existence or activity.
-
B.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
C.
homeVenueName
Indicates the name of the primary venue or location where an entity (such as a team, event, or organization) regularly hosts its home activities.
-
D.
homeVenueTown
chosen
Indicates the town or municipality where an entity’s primary or home venue is located.
-
E.
homeVenueCountry
Indicates the country in which an entity’s primary or home venue is located.
- F. None of above.
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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d65f8e488190a7675c3e585ca240 |
completed | June 29, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.