Triple
T8182469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalmette, Louisiana |
E191095
|
entity |
| Predicate | battlefieldPreservedAs |
P81308
|
FINISHED |
| Object | national historical park unit |
—
|
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: national historical park unit | Statement: [Chalmette, Louisiana, battlefieldPreservedAs, national historical park unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlefieldPreservedAs Context triple: [Chalmette, Louisiana, battlefieldPreservedAs, national historical park unit]
-
A.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
C.
battlefieldSector
Indicates a specific area or zone of a battlefield in which a military unit, action, or event is located or occurs.
-
D.
regionOfBattlesCommemorated
Indicates the geographic region where the battles being commemorated took place.
-
E.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
- F. None of above. chosen
Provenance (4 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4db8748190aa785e0c70fac497 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:40 p.m.