Triple
T526365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monmouth campaign |
E10926
|
entity |
| Predicate | placeOfMainEngagement |
P15172
|
FINISHED |
| Object | near Monmouth Court House, New Jersey |
—
|
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: near Monmouth Court House, New Jersey | Statement: [Monmouth campaign, placeOfMainEngagement, near Monmouth Court House, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfMainEngagement Context triple: [Monmouth campaign, placeOfMainEngagement, near Monmouth Court House, New Jersey]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
D.
firstCombatUseLocation
Indicates the location where something (typically a weapon, system, or tactic) was used in combat for the first time.
-
E.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
- F. None of above. chosen
Provenance (4 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d0d22081908aad915482d39e74 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.