Triple
T5546630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mercer |
E145423
|
entity |
| Predicate | casualtiesOpponentAtBattleOfRedBank |
P35438
|
FINISHED |
| Object | high Hessian casualties |
—
|
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: high Hessian casualties | Statement: [Fort Mercer, casualtiesOpponentAtBattleOfRedBank, high Hessian casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesOpponentAtBattleOfRedBank Context triple: [Fort Mercer, casualtiesOpponentAtBattleOfRedBank, high Hessian casualties]
-
A.
PatriotCasualties
Indicates that the event involves casualties suffered by patriot forces or supporters.
-
B.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
C.
resultOfPequotWar
Indicates that the subject entity is an outcome, consequence, or product that occurred as a result of the Pequot War.
-
D.
opponentInBattleOfCherbourg
Indicates that two entities were opposing sides against each other in the Battle of Cherbourg.
-
E.
casualtiesAssociatedWithEvent
chosen
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fdec3588190b0af7d2ca8e8ee9b |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.