Triple
T21281909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair X-6 |
E524546
|
entity |
| Predicate | programTermination |
P143593
|
FINISHED |
| Object | early 1960s |
—
|
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: early 1960s | Statement: [Convair X-6, programTermination, early 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programTermination Context triple: [Convair X-6, programTermination, early 1960s]
-
A.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
-
B.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
-
C.
cleanupProgram
Indicates that an entity is involved in or responsible for a program or initiative focused on cleaning up or removing waste, pollution, or unwanted materials.
-
D.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
E.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
- 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_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. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:02 p.m.