Triple
T34598254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakehurst, New Jersey |
E888376
|
entity |
| Predicate | eventNearby |
P121066
|
FINISHED |
| Object | Hindenburg disaster |
—
|
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: Hindenburg disaster | Statement: [Lakehurst, New Jersey, eventNearby, Hindenburg disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventNearby Context triple: [Lakehurst, New Jersey, eventNearby, Hindenburg disaster]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
hostedEventsNearby
Indicates that an entity has organized or is responsible for events occurring within a nearby geographic area relative to another reference point.
-
C.
weekendEvent
Indicates that an event occurs during the weekend period (typically Saturday and/or Sunday).
-
D.
associatedCityEvent
chosen
Indicates a relationship where a city is linked to, involved in, or serves as the location for a particular event.
-
E.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 2:03 a.m.