Triple
T6557031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Antrim |
E152474
|
entity |
| Predicate | reinforcements |
P3261
|
FINISHED |
| Object | British troops from Belfast |
—
|
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: British troops from Belfast | Statement: [Battle of Antrim, reinforcements, British troops from Belfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinforcements Context triple: [Battle of Antrim, reinforcements, British troops from Belfast]
-
A.
reinforcedIn
Indicates that one entity is strengthened, supported, or made more robust within, or as a result of conditions in, another entity or context.
-
B.
replenishment
Indicates the action or process of refilling or restoring a resource, supply, or quantity to a desired or original level.
-
C.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
E.
strengthens
chosen
Indicates that one entity increases the power, effectiveness, or resilience of another.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.