Triple
T38632145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitulation of Cahuenga |
E937476
|
entity |
| Predicate | combatantsDisarmed |
P186268
|
FINISHED |
| Object | Californio lancers and militia forces |
—
|
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: Californio lancers and militia forces | Statement: [Capitulation of Cahuenga, combatantsDisarmed, Californio lancers and militia forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantsDisarmed Context triple: [Capitulation of Cahuenga, combatantsDisarmed, Californio lancers and militia forces]
-
A.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
B.
disarmedAfter
chosen
Indicates that one entity has been deprived of its weapons or means of attack after a specified event or point in time in relation to another entity.
-
C.
unarmed
Indicates that an entity is not carrying or equipped with any weapons.
-
D.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
E.
enablesWeaponlessCombat
Indicates that an entity provides the capability for another entity to engage in combat without using weapons.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.