Triple
T35871432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S 32C reconnaissance variant |
E1037234
|
entity |
| Predicate | sharesAirframeWith |
P52744
|
FINISHED |
| Object | A 32A attack variant |
—
|
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: A 32A attack variant | Statement: [S 32C reconnaissance variant, sharesAirframeWith, A 32A attack variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesAirframeWith Context triple: [S 32C reconnaissance variant, sharesAirframeWith, A 32A attack variant]
-
A.
sharesAircraftWith
Indicates that two or more entities use, operate, or are associated with the same aircraft.
-
B.
airframeCommonalityWith
chosen
Indicates that two aircraft share the same or highly similar structural design and components in their airframes.
-
C.
airframeUsedFor
Indicates that a particular airframe is employed or designated for a specific use, role, or application.
-
D.
airframeNumber
Indicates the unique identifying number assigned to a specific aircraft’s structural frame within a fleet or system.
-
E.
sharesTrunkWith
Indicates that two entities have a common trunk or main stem from which they both extend or branch.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: May 3, 2026, 4:06 p.m.