Triple
T12293830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-214ON |
E293032
|
entity |
| Predicate | registrationExample |
P88876
|
FINISHED |
| Object |
RF‑64525
RF‑64525 is a specific Russian Tupolev Tu-214ON reconnaissance and observation aircraft used under the Open Skies Treaty program.
|
E975271
|
NE FINISHED |
How this triple was built (4 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: RF‑64525 | Statement: [Tupolev Tu-214ON, registrationExample, RF‑64525]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RF‑64525 Context triple: [Tupolev Tu-214ON, registrationExample, RF‑64525]
-
A.
RG45
RG45 is a postcode district within the RG (Reading) postcode area in England, covering parts of Crowthorne and the surrounding region in Berkshire.
-
B.
MF 67
MF 67 is a class of steel-wheeled electric multiple unit trains that have long served as a primary rolling stock type on the Paris Métro.
-
C.
RF-100A
The RF-100A was a specialized photo-reconnaissance version of the North American F-100 Super Sabre, adapted for high-speed, high-altitude intelligence-gathering missions.
-
D.
R540
R540 is a regional road in South Africa that serves as a connector route in the Mpumalanga province, linking towns such as Lydenburg to surrounding areas.
-
E.
FR-42
FR-42 is the ISO 3166-2 code designating the Loire department in central-eastern France.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RF‑64525 Triple: [Tupolev Tu-214ON, registrationExample, RF‑64525]
Generated description
RF‑64525 is a specific Russian Tupolev Tu-214ON reconnaissance and observation aircraft used under the Open Skies Treaty program.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RF‑64525 Target entity description: RF‑64525 is a specific Russian Tupolev Tu-214ON reconnaissance and observation aircraft used under the Open Skies Treaty program.
-
A.
RG45
RG45 is a postcode district within the RG (Reading) postcode area in England, covering parts of Crowthorne and the surrounding region in Berkshire.
-
B.
MF 67
MF 67 is a class of steel-wheeled electric multiple unit trains that have long served as a primary rolling stock type on the Paris Métro.
-
C.
RF-100A
The RF-100A was a specialized photo-reconnaissance version of the North American F-100 Super Sabre, adapted for high-speed, high-altitude intelligence-gathering missions.
-
D.
R540
R540 is a regional road in South Africa that serves as a connector route in the Mpumalanga province, linking towns such as Lydenburg to surrounding areas.
-
E.
FR-42
FR-42 is the ISO 3166-2 code designating the Loire department in central-eastern France.
- F. None of above. chosen
Provenance (5 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d23def88190adbaa282dd03d6c6 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e79bf548190bf7f314222ed1ed1 |
completed | May 2, 2026, 3:55 p.m. |
| NEDg | Description generation | batch_69f62260d6708190808e52935a27e2c1 |
completed | May 2, 2026, 4:12 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f6230f4c8081908a759efa43b4800b |
completed | May 2, 2026, 4:15 p.m. |
Created at: April 8, 2026, 9:52 p.m.