Triple
T24131374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce BR710 |
E597960
|
entity |
| Predicate | natoStockNumber |
P6062
|
FINISHED |
| Object | 2840-99-000-0000 (generic placeholder) |
—
|
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: 2840-99-000-0000 (generic placeholder) | Statement: [Rolls-Royce BR710, natoStockNumber, 2840-99-000-0000 (generic placeholder)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natoStockNumber Context triple: [Rolls-Royce BR710, natoStockNumber, 2840-99-000-0000 (generic placeholder)]
-
A.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
-
B.
UNSNumber
Indicates that an entity is associated with a specific United Nations (UN) number used to identify hazardous substances or dangerous goods.
-
C.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
D.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
E.
airForceUnitNumber
Indicates the identifying number assigned to an air force unit in a military organizational structure.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7788788190a71ad080fc2890a8 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:25 p.m.