Triple
T22313078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French ship Brave |
E551569
|
entity |
| Predicate | typeOfConflictParticipatedIn |
P1397
|
FINISHED |
| Object | naval battle |
—
|
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: naval battle | Statement: [French ship Brave, typeOfConflictParticipatedIn, naval battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictParticipatedIn Context triple: [French ship Brave, typeOfConflictParticipatedIn, naval battle]
-
A.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
B.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
D.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
E.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15750f76c81909d6f788928f503f1 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.