Triple
T34119033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HS 125 Series 600 |
E875061
|
entity |
| Predicate | civilCertification |
P13210
|
FINISHED |
| Object | civil transport aircraft |
—
|
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: civil transport aircraft | Statement: [HS 125 Series 600, civilCertification, civil transport aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilCertification Context triple: [HS 125 Series 600, civilCertification, civil transport aircraft]
-
A.
canCertify
Indicates that one entity has the authority or capability to officially certify another entity or its attributes.
-
B.
legalRecognition
Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
-
C.
civilVariant
Indicates a relationship where one item is a civil (non-military or civilian-use) version or counterpart of another.
-
D.
certificationBy
chosen
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
E.
isCivil
Indicates that one party behaves in a polite, respectful, and non-hostile manner toward another.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.