Triple
T21281901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair X-6 |
E524546
|
entity |
| Predicate | testbedPlan |
P28585
|
FINISHED |
| Object | use of modified B-36 airframe |
—
|
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: use of modified B-36 airframe | Statement: [Convair X-6, testbedPlan, use of modified B-36 airframe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testbedPlan Context triple: [Convair X-6, testbedPlan, use of modified B-36 airframe]
-
A.
testbedFor
chosen
Indicates that one entity serves as an environment or platform used to develop, experiment with, or evaluate another entity.
-
B.
testPlanUpdated
Indicates that an existing test plan has been modified or its details have been updated.
-
C.
plannedNumberOfTests
Indicates the total count of tests that are intended or scheduled to be conducted for a given context or period.
-
D.
establishesTest
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
E.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d249fc8190b0b310467ddeac3c |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:02 p.m.