Triple
T20571027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bussaco |
E505096
|
entity |
| Predicate | strengthAngloPortuguese |
P39451
|
FINISHED |
| Object | approximately 50,000 troops |
—
|
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 50,000 troops | Statement: [Battle of Bussaco, strengthAngloPortuguese, approximately 50,000 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthAngloPortuguese Context triple: [Battle of Bussaco, strengthAngloPortuguese, approximately 50,000 troops]
-
A.
strength_British_side
chosen
Indicates the level or measure of military or strategic power possessed by the British side in a given context.
-
B.
fleetStrengthEnglish
Indicates the relative military or naval power level associated with a fleet, expressed or categorized in English terms.
-
C.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
D.
strengthUnionEngaged
Indicates that a union is actively involved or participating in efforts to exert or demonstrate strength, power, or influence.
-
E.
EnglishStrength
Indicates the degree or level of proficiency or capability in using the English language.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a5b0688190b45d0fa993c4765c |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.