Triple
T2023670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exocet |
E44159
|
entity |
| Predicate | combatReputation |
P24407
|
FINISHED |
| Object | highly effective anti-ship weapon |
—
|
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: highly effective anti-ship weapon | Statement: [Exocet, combatReputation, highly effective anti-ship weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatReputation Context triple: [Exocet, combatReputation, highly effective anti-ship weapon]
-
A.
tacticalReputation
Indicates the perceived level of skill, reliability, or effectiveness an entity has in planning and executing tactics within a given context.
-
B.
militaryReputation
chosen
Indicates the perceived standing or esteem of an entity based on its past or present military performance, conduct, or capabilities.
-
C.
championshipReputation
Indicates the recognized status or esteem an entity holds based on its history of success or performance in championships or major competitive titles.
-
D.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
combatRecord
Indicates that an entity maintains a documented history of its participation in combat or battles.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.