Triple
T3317423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance |
E69713
|
entity |
| Predicate | navalWarfareType |
P1403
|
FINISHED |
| Object | frigate warfare |
—
|
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: frigate warfare | Statement: [Alliance, navalWarfareType, frigate warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalWarfareType Context triple: [Alliance, navalWarfareType, frigate warfare]
-
A.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
B.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
C.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
navalEra
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb113cb6c8190989b06476f6015fd |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.