Triple
T25237245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halifax Mk VI |
E632370
|
entity |
| Predicate | hasUndercarriage |
P67281
|
FINISHED |
| Object | retractable tailwheel undercarriage |
—
|
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: retractable tailwheel undercarriage | Statement: [Halifax Mk VI, hasUndercarriage, retractable tailwheel undercarriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndercarriage Context triple: [Halifax Mk VI, hasUndercarriage, retractable tailwheel undercarriage]
-
A.
hasUndercarriageType
chosen
Indicates the specific type or configuration of undercarriage that an object (typically a vehicle or machine) possesses.
-
B.
hasCarriageShed
Indicates that an entity possesses or includes a shed or structure specifically used for storing or housing carriages.
-
C.
hasCargoAccess
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
D.
hasTrunkCarvings
Indicates that an entity (typically a tree) possesses carvings or engravings on its trunk.
-
E.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:07 p.m.