Triple
T1505850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Street and Addison Street |
E33898
|
entity |
| Predicate | hasNearbyEventType |
P29453
|
FINISHED |
| Object | Major League Baseball games |
—
|
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: Major League Baseball games | Statement: [Clark Street and Addison Street, hasNearbyEventType, Major League Baseball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyEventType Context triple: [Clark Street and Addison Street, hasNearbyEventType, Major League Baseball games]
-
A.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasNearbyPeak
Indicates that one location has another peak situated close to it in geographic space.
-
D.
hasNearbySquare
Indicates that one entity has at least one square-shaped entity located close to it in space.
-
E.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a90582f2548190bc0a6bdcd6d9d015 |
completed | March 5, 2026, 4:24 a.m. |
Created at: March 4, 2026, 7:24 p.m.