Triple
T38372095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of George Floyd |
E892611
|
entity |
| Predicate | occurredAtIntersection |
P24433
|
FINISHED |
| Object | East 38th Street and Chicago Avenue |
—
|
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: East 38th Street and Chicago Avenue | Statement: [murder of George Floyd, occurredAtIntersection, East 38th Street and Chicago Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredAtIntersection Context triple: [murder of George Floyd, occurredAtIntersection, East 38th Street and Chicago Avenue]
-
A.
locatedAtIntersectionOf
Indicates that something is situated at the point where two or more paths, roads, or boundaries cross or meet.
-
B.
occursAt
chosen
Indicates that an event or action takes place at a specific time or location.
-
C.
isPlayedOnIntersections
Indicates that an activity or game takes place specifically at the intersection points of a defined grid or set of crossing lines.
-
D.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.