Triple
T22014846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union II Corps line |
E543681
|
entity |
| Predicate | primaryEngagementDate |
P146280
|
FINISHED |
| Object | July 3, 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 3, 1863 | Statement: [Union II Corps line, primaryEngagementDate, July 3, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEngagementDate Context triple: [Union II Corps line, primaryEngagementDate, July 3, 1863]
-
A.
primaryEngagement
Indicates the main or most significant interaction, involvement, or relationship that an entity has with another entity or activity.
-
B.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
C.
engagedAt
Indicates that two entities became formally engaged to be married at a specific time or event.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
engagedOnDate
Indicates that two entities entered into an engagement or formal commitment on a specific calendar date.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a774548190bcd98dc28f2d2c5f |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:22 p.m.