Triple
T12065882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lawrence |
E287293
|
entity |
| Predicate | statusDuringBattleOfLakeErie |
P103019
|
FINISHED |
| Object | heavily damaged |
—
|
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: heavily damaged | Statement: [USS Lawrence, statusDuringBattleOfLakeErie, heavily damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringBattleOfLakeErie Context triple: [USS Lawrence, statusDuringBattleOfLakeErie, heavily damaged]
-
A.
statusDuringBattleOfPlattsburgh
Indicates the role, condition, or situation an entity held specifically during the Battle of Plattsburgh.
-
B.
positionOnWarOf1812
Indicates a stance, opinion, or alignment that an entity holds regarding the War of 1812.
-
C.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
D.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:48 p.m.