Triple
T19332434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC-150 Polaris |
E483529
|
entity |
| Predicate | numberBuiltForRCAF |
P2091
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [CC-150 Polaris, numberBuiltForRCAF, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberBuiltForRCAF Context triple: [CC-150 Polaris, numberBuiltForRCAF, 5]
-
A.
numberBuiltForRNZAF
Indicates the total quantity of items that were constructed specifically for the Royal New Zealand Air Force (RNZAF).
-
B.
appliedToAircraftBuiltBy
Indicates that something (such as a regulation, modification, or action) is applied specifically to aircraft that were built by a particular manufacturer or builder.
-
C.
armamentAsBuilt
Indicates the weaponry or armament configuration that an object (such as a vehicle, vessel, or structure) originally had when it was first constructed or completed.
-
D.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
-
E.
numberBuilt
chosen
Indicates the total count of items or structures that have been constructed or produced.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61642f49c81909226cfd701f7c139 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.