Triple
T11040673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Saint-Eustache |
E261004
|
entity |
| Predicate | outcomeForPatriotes |
P97439
|
FINISHED |
| Object | Patriote forces routed |
—
|
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: Patriote forces routed | Statement: [Battle of Saint-Eustache, outcomeForPatriotes, Patriote forces routed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForPatriotes Context triple: [Battle of Saint-Eustache, outcomeForPatriotes, Patriote forces routed]
-
A.
PatriotsScore
Indicates that a scoring event or point total is attributed to the Patriots in a game or contest.
-
B.
PatriotsHomeAdvantageReputation
Indicates that the New England Patriots are perceived to gain a notable competitive edge when playing at their home venue.
-
C.
strengthPatriots
Indicates a relationship where the strength, power, or capability associated with a group referred to as "Patriots" is being expressed or evaluated.
-
D.
touchdownsWithPatriots
Indicates the number of touchdowns a player scored while playing for the New England Patriots.
-
E.
PatriotsTeamCity
Indicates the city that serves as the home location for the Patriots team.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980050948190ae7b187da5b776ca |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.