Triple
T5546629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mercer |
E145423
|
entity |
| Predicate | resultOfBattleOfRedBank |
P19109
|
FINISHED |
| Object | American victory |
—
|
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: American victory | Statement: [Fort Mercer, resultOfBattleOfRedBank, American victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfRedBank Context triple: [Fort Mercer, resultOfBattleOfRedBank, American victory]
-
A.
resultOfPequotWar
Indicates that the subject entity is an outcome, consequence, or product that occurred as a result of the Pequot War.
-
B.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
C.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
D.
isFirstMajorBattleOf
Indicates that a battle is the earliest significant or primary large-scale engagement within a particular war, campaign, or conflict.
-
E.
riverCrossedByAllies
Indicates that the river was traversed or crossed by allied forces.
- 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.