Triple
T22476330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charonne |
E555638
|
entity |
| Predicate | nearEventDate |
P45864
|
FINISHED |
| Object | 8 February 1962 |
—
|
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: 8 February 1962 | Statement: [Charonne, nearEventDate, 8 February 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearEventDate Context triple: [Charonne, nearEventDate, 8 February 1962]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
C.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
-
D.
hasNearbyEvent
chosen
Indicates that an event occurs close in space or time to the referenced entity.
-
E.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be48cec8190baff90f8566a85d0 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.