Triple
T17120988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutan VariEze |
E415462
|
entity |
| Predicate | controlSurface |
P21443
|
FINISHED |
| Object | elevons on canard |
—
|
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: elevons on canard | Statement: [Rutan VariEze, controlSurface, elevons on canard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSurface Context triple: [Rutan VariEze, controlSurface, elevons on canard]
-
A.
controlSurfaces
chosen
Indicates that one entity functions as a control surface or set of control surfaces used to influence, steer, or regulate the behavior or state of another entity.
-
B.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
C.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
D.
controlInteraction
Indicates an interaction in which one entity directs, regulates, or constrains the behavior or state of another.
-
E.
controlLink
Indicates a relationship where one entity exerts control, influence, or governing authority over another entity or process.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.