Triple
T3106958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Moore’s Creek Bridge |
E64854
|
entity |
| Predicate | LoyalistStrength |
P20427
|
FINISHED |
| Object | approximately 1,600 men |
—
|
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: approximately 1,600 men | Statement: [Battle of Moore’s Creek Bridge, LoyalistStrength, approximately 1,600 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LoyalistStrength Context triple: [Battle of Moore’s Creek Bridge, LoyalistStrength, approximately 1,600 men]
-
A.
loyalistsBase
Indicates that a group of loyalists is based at, or primarily operates from, a particular location or base.
-
B.
loyalistUnitOf
Indicates that one unit is a loyal or devoted supporter, follower, or subordinate of another entity.
-
C.
RoyalistForceStrength
chosen
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
D.
WilliamiteStrength
Indicates the degree of military, political, or social power held by the Williamite side in a given context or period.
-
E.
strength_British_side
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.