Triple
T13567294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argus As 014 |
E324070
|
entity |
| Predicate | mountingPositionOnV1 |
P29518
|
FINISHED |
| Object | above fuselage |
—
|
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: above fuselage | Statement: [Argus As 014, mountingPositionOnV1, above fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountingPositionOnV1 Context triple: [Argus As 014, mountingPositionOnV1, above fuselage]
-
A.
mountingLocation
chosen
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
C.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
D.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
E.
mountType
Indicates the manner or configuration in which one object is mounted or attached to 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00e0188819094fde44f85adb69c |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.