Triple
T31949194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishpot |
E815732
|
entity |
| Predicate | hasNATOCodeNamePattern |
P6062
|
FINISHED |
| Object | NATO fighter names starting with F |
—
|
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: NATO fighter names starting with F | Statement: [Fishpot, hasNATOCodeNamePattern, NATO fighter names starting with F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNATOCodeNamePattern Context triple: [Fishpot, hasNATOCodeNamePattern, NATO fighter names starting with F]
-
A.
hasNATOContext
Indicates that something is related to, influenced by, or situated within the context of NATO, its activities, policies, or structures.
-
B.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
C.
isNATOBase
Indicates that a location functions as a military base operated by or officially affiliated with NATO.
-
D.
hasOfficialNamePattern
Indicates that an entity’s official name follows or matches a specified naming pattern or format.
-
E.
introducedAsNATOReportingNameFor
Indicates that one entity was designated and announced as the official NATO reporting name for another entity.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 12:07 a.m.