Triple
T9164771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Philippi |
E219921
|
entity |
| Predicate | seriesOfEngagements |
P76458
|
FINISHED |
| Object | two main battles |
—
|
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: two main battles | Statement: [Battle of Philippi, seriesOfEngagements, two main battles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesOfEngagements Context triple: [Battle of Philippi, seriesOfEngagements, two main battles]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
seriesOf
chosen
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
C.
partOfSeriesOfEvents
Indicates that an event is one element within a larger, ordered sequence of related events.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2ee64c8190a9a5abafe5d0b086 |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.