Triple
T830707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-29 Superfortress |
E17956
|
entity |
| Predicate | developmentProgramName |
P20491
|
FINISHED |
| Object | Model 345 |
—
|
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: Model 345 | Statement: [B-29 Superfortress, developmentProgramName, Model 345]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentProgramName Context triple: [B-29 Superfortress, developmentProgramName, Model 345]
-
A.
developmentProgram
Indicates a structured initiative or plan designed to improve, advance, or build the capabilities, resources, or conditions of a target group, system, or area over time.
-
B.
developmentAcademy
Indicates a relationship where an academy is responsible for or involved in the development, training, or educational advancement of individuals or groups.
-
C.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
D.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
E.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb384988190949d2df65662f76d |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.