Triple
T27904015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Corps (Union Army) |
E705718
|
entity |
| Predicate | engagedStrengthAt |
P163975
|
FINISHED |
| Object | Battle of Gettysburg |
—
|
NE NERFINISHED |
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: Battle of Gettysburg | Statement: [III Corps (Union Army), engagedStrengthAt, Battle of Gettysburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagedStrengthAt Context triple: [III Corps (Union Army), engagedStrengthAt, Battle of Gettysburg]
-
A.
engagedAt
Indicates that two entities became formally engaged to be married at a specific time or event.
-
B.
engagedOn
Indicates that two entities are committed to be married to each other as of a specific date or point in time.
-
C.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
engagementScale
Indicates the degree or intensity of involvement, interest, or participation in an activity, interaction, or 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 6:44 p.m.