Triple
T34438033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Stick-Up at Brinks |
E884018
|
entity |
| Predicate | placeOfSubjectEvent |
P165186
|
FINISHED |
| Object | Boston |
—
|
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: Boston | Statement: [The Big Stick-Up at Brinks, placeOfSubjectEvent, Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfSubjectEvent Context triple: [The Big Stick-Up at Brinks, placeOfSubjectEvent, Boston]
-
A.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
B.
tookPlaceAtLocation
chosen
Indicates that an event or action occurred at a specific location.
-
C.
takesPlace
Indicates that an event or action occurs or is situated at a particular time, place, or context.
-
D.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
E.
subjectOfEvent
Indicates that an entity participates in or is involved in a particular event as one of its primary actors or focal points.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 2 a.m.