Triple
T12113560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls‑Royce Vulture I |
E288496
|
entity |
| Predicate | applicationStage |
P9657
|
FINISHED |
| Object | early production bombers |
—
|
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 production bombers | Statement: [Rolls‑Royce Vulture I, applicationStage, early production bombers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationStage Context triple: [Rolls‑Royce Vulture I, applicationStage, early production bombers]
-
A.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
B.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
C.
investmentStage
Indicates the phase or maturity level a company or project is in with respect to receiving investment or funding.
-
D.
staging
Indicates the process of arranging, organizing, or setting up elements in preparation for a main event, performance, or deployment.
-
E.
campaignPhase
Indicates the specific stage or period within the lifecycle of a campaign in which an entity or activity currently occurs.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.