Triple
T21409658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Millstone |
E528132
|
entity |
| Predicate | impactOnMorale |
P103390
|
FINISHED |
| Object | boosted Patriot morale in 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: boosted Patriot morale in New Jersey | Statement: [Battle of Millstone, impactOnMorale, boosted Patriot morale in New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnMorale Context triple: [Battle of Millstone, impactOnMorale, boosted Patriot morale in New Jersey]
-
A.
impactOnLeader
Indicates that one entity has an effect, influence, or consequence on a leader within a given context.
-
B.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
impactDescription
chosen
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
E.
impactOnField
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b40eb48190ae03532de9841cba |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:41 p.m.