Triple
T11684302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Eagle |
E277698
|
entity |
| Predicate | resultOfEngagementAtBattleOfPlattsburgh |
P19109
|
FINISHED |
| Object | victorious |
—
|
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: victorious | Statement: [USS Eagle, resultOfEngagementAtBattleOfPlattsburgh, victorious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfEngagementAtBattleOfPlattsburgh Context triple: [USS Eagle, resultOfEngagementAtBattleOfPlattsburgh, victorious]
-
A.
statusDuringBattleOfPlattsburgh
Indicates the role, condition, or situation an entity held specifically during the Battle of Plattsburgh.
-
B.
locationDuringBattleOfPlattsburgh
Indicates the location of an entity specifically during the time of the Battle of Plattsburgh.
-
C.
resultOfPequotWar
Indicates that the subject entity is an outcome, consequence, or product that occurred as a result of the Pequot War.
-
D.
engagementOutcomeAtBattleOfIquique
Indicates the result or outcome of a specific party’s engagement in the Battle of Iquique.
-
E.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a463f6448190a4c8e1651a2bd905 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.