Triple
T34434253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Allied reporting name system |
E883909
|
entity |
| Predicate | namingRuleFor |
P2555
|
FINISHED |
| Object | Soviet fighter aircraft |
—
|
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: Soviet fighter aircraft | Statement: [NATO Allied reporting name system, namingRuleFor, Soviet fighter aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRuleFor Context triple: [NATO Allied reporting name system, namingRuleFor, Soviet fighter aircraft]
-
A.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
B.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
C.
namingConventionContext
Indicates the contextual rules or patterns that govern how something is named within a particular system or setting.
-
D.
namingConventionRegion
Indicates that there is a specific regional or locale-based rule or pattern governing how something is named.
-
E.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
- 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.