Triple
T21955144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Newtown |
E542167
|
entity |
| Predicate | strengthOpposing |
P30658
|
FINISHED |
| Object | approximately 800–1,200 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 800–1,200 men | Statement: [Battle of Newtown, strengthOpposing, approximately 800–1,200 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthOpposing Context triple: [Battle of Newtown, strengthOpposing, approximately 800–1,200 men]
-
A.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
B.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
C.
opponentStrength
chosen
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
-
D.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
-
E.
strongerDuring
Indicates that one entity exhibits greater strength or intensity than another specifically during a given time period or event.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243f46dc819097e4a1849af7fba4 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.