Triple
T3274794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fontenoy |
E68733
|
entity |
| Predicate | locationRelativeToCity |
P43164
|
FINISHED |
| Object | near Tournai |
—
|
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: near Tournai | Statement: [Battle of Fontenoy, locationRelativeToCity, near Tournai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToCity Context triple: [Battle of Fontenoy, locationRelativeToCity, near Tournai]
-
A.
locationRelativeToIP
Indicates a spatial or geographic relationship between an entity and a given IP address’s inferred location.
-
B.
relativeHeightAboveCity
Indicates the vertical height of an entity measured above the reference elevation level of a specified city.
-
C.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
D.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
E.
locationSignedNear
chosen
Indicates that an entity’s location is in close physical proximity to another specified place or reference point.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff8a440819092509bc8511b2785 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.