Triple
T34721788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farragut Monument |
E1000934
|
entity |
| Predicate | honorsBattle |
P62393
|
FINISHED |
| Object | Battle of Mobile Bay |
—
|
NE NERFINISHED |
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: Battle of Mobile Bay | Statement: [Farragut Monument, honorsBattle, Battle of Mobile Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsBattle Context triple: [Farragut Monument, honorsBattle, Battle of Mobile Bay]
-
A.
oftenBattles
Indicates that one entity frequently engages in conflicts, fights, or confrontations with another entity.
-
B.
battleHonored
chosen
Indicates that an entity has been formally recognized or commemorated for its participation or valor in a battle or military conflict.
-
C.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.