Triple
T32440859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Henry |
E829009
|
entity |
| Predicate | battleNearby |
P39414
|
FINISHED |
| Object | Battle of the Capes (1781 naval battle off the Virginia Capes) |
—
|
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 the Capes (1781 naval battle off the Virginia Capes) | Statement: [Cape Henry, battleNearby, Battle of the Capes (1781 naval battle off the Virginia Capes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleNearby Context triple: [Cape Henry, battleNearby, Battle of the Capes (1781 naval battle off the Virginia Capes)]
-
A.
حمله
Indicates an aggressive action in which one entity attacks, assaults, or launches an offensive against another.
-
B.
battleInvolvedIn
Indicates that an entity participated as a combatant or directly took part in a specific battle or military engagement.
-
C.
battlefieldOf
chosen
Indicates that a location is the site where a particular battle or military engagement took place.
-
D.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
E.
battleRelatedTo
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e2652881909198964213886476 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.