Triple
T24301914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing E-3D Sentry AEW1 |
E612421
|
entity |
| Predicate | numberBuiltForRAF |
P155477
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Boeing E-3D Sentry AEW1, numberBuiltForRAF, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberBuiltForRAF Context triple: [Boeing E-3D Sentry AEW1, numberBuiltForRAF, 7]
-
A.
numberBuiltForRNZAF
Indicates the total quantity of items that were constructed specifically for the Royal New Zealand Air Force (RNZAF).
-
B.
RAFBaseRedevelopment
Indicates the process or state of redeveloping a Royal Air Force (RAF) base site for new or alternative uses.
-
C.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
D.
poweredFirstOperationalRAFJet
Indicates that the subject provided the propulsion for the first jet aircraft to enter operational service with the Royal Air Force.
-
E.
RAAFQuantity
Indicates a relationship where a specific quantity or amount is associated with, measured by, or attributed to an entity or resource within the RAAF context.
- F. None of above. chosen
Provenance (4 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29222d3008190af765d62787ee334 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:15 a.m.