Triple
T2665342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Manchester |
E55620
|
entity |
| Predicate | designIssue |
P41290
|
FINISHED |
| Object | unreliable Rolls‑Royce Vulture engines |
—
|
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: unreliable Rolls‑Royce Vulture engines | Statement: [Avro Manchester, designIssue, unreliable Rolls‑Royce Vulture engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designIssue Context triple: [Avro Manchester, designIssue, unreliable Rolls‑Royce Vulture engines]
-
A.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designStandardizedIn
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
-
C.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designSpecifiedBy
Indicates that the design or specification of one entity is defined, authored, or determined by another entity.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96ed2748190a4feae98199b459d |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:54 p.m.