Triple
T35779846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747-400F |
E1034405
|
entity |
| Predicate | noseDoorOpening |
P154922
|
FINISHED |
| Object | upward-hinged nose section |
—
|
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: upward-hinged nose section | Statement: [Boeing 747-400F, noseDoorOpening, upward-hinged nose section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noseDoorOpening Context triple: [Boeing 747-400F, noseDoorOpening, upward-hinged nose section]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
HolyDoorOpeningBy
Indicates that a holy door is opened through the action or authority of a specified agent.
-
C.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
D.
hasDoorsOperation
chosen
Indicates that an entity has a specific type or mode of operation for its doors (e.g., how they open, close, or are controlled).
-
E.
hasDoorSide
Indicates that one entity represents a specific side or face of a door in relation to another entity.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.