Triple
T446803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manassas National Battlefield Park |
E7038
|
entity |
| Predicate | battleDateCommemorated |
P828
|
FINISHED |
| Object | July 21, 1861 |
—
|
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: July 21, 1861 | Statement: [Manassas National Battlefield Park, battleDateCommemorated, July 21, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDateCommemorated Context triple: [Manassas National Battlefield Park, battleDateCommemorated, July 21, 1861]
-
A.
commemoratedOn
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
B.
commemorationDate
chosen
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
C.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
D.
commemoratesConflict
Indicates a relationship where something (such as a monument, event, or work) serves to remember, honor, or mark a specific conflict or war.
-
E.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.