Triple
T34434254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Allied reporting name system |
E883909
|
entity |
| Predicate | fighterNamingRule |
P118939
|
FINISHED |
| Object | names beginning with letter 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: names beginning with letter F | Statement: [NATO Allied reporting name system, fighterNamingRule, names beginning with letter F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighterNamingRule Context triple: [NATO Allied reporting name system, fighterNamingRule, names beginning with letter F]
-
A.
fighterNumber
Indicates the identifying number assigned to a fighter within a given context or event.
-
B.
fighter2Nickname
Indicates the nickname or moniker associated with the second fighter in a matchup or comparison.
-
C.
fighter1Nickname
Indicates that one entity is the nickname used by or associated with the first fighter in a fighting matchup or event.
-
D.
natoReportingNameOfBaseAircraft
Indicates that one entity is the NATO reporting name assigned to the other entity, which is the original (base) aircraft model.
-
E.
namedAccordingTo
chosen
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.