Triple
T20726822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Division, XII Corps |
E509456
|
entity |
| Predicate | engagedOnDate |
P141272
|
FINISHED |
| Object | 1863-07-02 |
—
|
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: 1863-07-02 | Statement: [1st Division, XII Corps, engagedOnDate, 1863-07-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagedOnDate Context triple: [1st Division, XII Corps, engagedOnDate, 1863-07-02]
-
A.
engagementDate
Indicates the date on which two entities formally become engaged or committed to a relationship or agreement.
-
B.
engagedAt
Indicates that two entities became formally engaged to be married at a specific time or event.
-
C.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
D.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
-
E.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e8b020819091d5788b90215ead |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:29 p.m.