Triple
T9297936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed A-12 program |
E223686
|
entity |
| Predicate | numberOfAirframesBuilt |
P5710
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Lockheed A-12 program, numberOfAirframesBuilt, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAirframesBuilt Context triple: [Lockheed A-12 program, numberOfAirframesBuilt, 13]
-
A.
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.
-
B.
numberOfFuselages
Indicates the quantity of fuselages associated with or contained in a given object or configuration.
-
C.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
-
D.
appliedToAircraftDesignedBy
Indicates that something (such as a component, system, or regulation) is applied to an aircraft that was designed by a specified designer or organization.
-
E.
numberOfPlanes
chosen
Indicates the quantity of planes associated with or involved in a given entity or situation.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089e3ae88190aa4181cdd85a67b8 |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.