Triple
T12895955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Molino del Rey |
E308492
|
entity |
| Predicate | USStrength |
P81774
|
FINISHED |
| Object | approximately 3,400 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 3,400 troops | Statement: [Battle of Molino del Rey, USStrength, approximately 3,400 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USStrength Context triple: [Battle of Molino del Rey, USStrength, approximately 3,400 troops]
-
A.
USProvides
Indicates that the United States supplies, furnishes, or makes available something (such as aid, resources, services, or support) to another entity.
-
B.
USForceStrength
chosen
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
C.
U.S.component
Indicates that something is a constituent part, subdivision, or member unit within the United States.
-
D.
allyOfUnitedStates
Indicates a relationship where an entity maintains a supportive, cooperative, or formally allied partnership with the United States.
-
E.
strengthGovernmentForces
Indicates the level or degree of military or coercive power held or exerted by government forces 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.