Triple
T14672329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fontenoy, Wallonia, Belgium |
E344543
|
entity |
| Predicate | historicalEventTypeAtLocation |
P2107
|
FINISHED |
| Object | 18th-century European battle |
—
|
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: 18th-century European battle | Statement: [Fontenoy, Wallonia, Belgium, historicalEventTypeAtLocation, 18th-century European battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventTypeAtLocation Context triple: [Fontenoy, Wallonia, Belgium, historicalEventTypeAtLocation, 18th-century European battle]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
C.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
D.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb55064cc8190b9669d0b2da61825 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.