Triple
T1017122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cemetery Hill |
E21955
|
entity |
| Predicate | dateOfMajorEngagement |
P20058
|
FINISHED |
| Object | July 1, 1863 |
—
|
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 1, 1863 | Statement: [Cemetery Hill, dateOfMajorEngagement, July 1, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMajorEngagement Context triple: [Cemetery Hill, dateOfMajorEngagement, July 1, 1863]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
endDateOfMajorBattle
chosen
Indicates the calendar date on which a major battle or significant military engagement came to an end.
-
C.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
D.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
E.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.