Triple
T14939989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Williamsburg |
E372497
|
entity |
| Predicate | isEarlyWarBattle |
P116759
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Williamsburg, isEarlyWarBattle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEarlyWarBattle Context triple: [Battle of Williamsburg, isEarlyWarBattle, true]
-
A.
isEarlyClashIn
Indicates that one event or interaction occurs earlier than and conflicts with another within a specified context or timeframe.
-
B.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
C.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
D.
earlyWar
Indicates that the war or conflict occurred in an early phase or at an earlier-than-typical point in a relevant timeline or sequence.
-
E.
isPostwarRound
Indicates that an event, activity, or phase occurs after the conclusion of a war or major conflict.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64a2f24819099b21566756668a2 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:38 a.m.