Triple
T16347937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smohain |
E396981
|
entity |
| Predicate | nearBattlefieldSector |
P21619
|
FINISHED |
| Object | eastern sector of the Waterloo battlefield |
—
|
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: eastern sector of the Waterloo battlefield | Statement: [Smohain, nearBattlefieldSector, eastern sector of the Waterloo battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearBattlefieldSector Context triple: [Smohain, nearBattlefieldSector, eastern sector of the Waterloo battlefield]
-
A.
battlefieldSector
Indicates a specific area or zone of a battlefield in which a military unit, action, or event is located or occurs.
-
B.
nearbyBattlefield
chosen
Indicates that one entity is located close to or in the immediate vicinity of a battlefield.
-
C.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
D.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
E.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da1038d88190b8292cfe71bc4f2a |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.