Triple
T10345280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce AE 3007A1/3 |
E243728
|
entity |
| Predicate | engineFamily |
P18926
|
FINISHED |
| Object | AE 3007 |
E236969
|
NE 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: AE 3007 | Statement: [Rolls-Royce AE 3007A1/3, engineFamily, AE 3007]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AE 3007 Context triple: [Rolls-Royce AE 3007A1/3, engineFamily, AE 3007]
-
A.
AE 3007A
chosen
The AE 3007A is a high-bypass turbofan engine developed by Rolls-Royce for regional jet aircraft.
-
B.
A377
A377 is a primary road in Devon, England, linking the town of Barnstaple with Exeter and serving as an important regional route.
-
C.
ME 133
ME 133 is a state highway in Maine that serves as a regional connector route between several central Maine communities.
-
D.
AER
AER is a leading peer-reviewed academic journal in economics published by the American Economic Association.
-
E.
AER
AER is the three-letter IATA airport code for Sochi International Airport, serving the Black Sea resort city of Sochi in Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e923e3d08190971073ce41ff860f |
completed | April 7, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7507f708c8190b8cf684704a6e47d |
completed | April 9, 2026, 7:08 a.m. |
Created at: April 6, 2026, 11:56 a.m.