Triple
T14878218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark I |
E349923
|
entity |
| Predicate | safetyLimitation |
P99
|
FINISHED |
| Object | unstable flight system |
—
|
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: unstable flight system | Statement: [Mark I, safetyLimitation, unstable flight system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyLimitation Context triple: [Mark I, safetyLimitation, unstable flight system]
-
A.
securityLimitation
Indicates a constraint, restriction, or boundary imposed for security purposes on what actions, access, or operations are allowed between entities.
-
B.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
C.
showsLimitationOf
Indicates that one entity reveals, demonstrates, or makes apparent the limitations, weaknesses, or constraints of another entity.
-
D.
safetyRequirement
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
E.
safetyRationale
Indicates the reasoning or justification provided to explain how and why something is considered safe or made safe.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.