Triple
T37871524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair 580 |
E944616
|
entity |
| Predicate | conversionProgramStart |
P192114
|
FINISHED |
| Object | 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: 1960s | Statement: [Convair 580, conversionProgramStart, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionProgramStart Context triple: [Convair 580, conversionProgramStart, 1960s]
-
A.
conversionProgram
Indicates a program or process that transforms something from one form, state, or type into another.
-
B.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
C.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
D.
conversionPractice
Indicates engaging in activities or exercises aimed at improving one's ability to convert or persuade others, typically in a religious, sales, or ideological context.
-
E.
conversionPlan
Indicates a planned or intended process of transforming or converting one state, format, or condition into another.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:19 p.m.