Triple
T7359278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cape Ortegal |
E169703
|
entity |
| Predicate | resultingEvent |
P59870
|
FINISHED |
| Object | capture of four French ships of the line |
—
|
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: capture of four French ships of the line | Statement: [Battle of Cape Ortegal, resultingEvent, capture of four French ships of the line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultingEvent Context triple: [Battle of Cape Ortegal, resultingEvent, capture of four French ships of the line]
-
A.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
B.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
D.
resolutionEvent
Indicates an event or action through which a previously existing issue, conflict, or problem is brought to a conclusion or resolved.
-
E.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.