Triple
T13012704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers J 1 |
E322459
|
entity |
| Predicate | controlSurfacesMaterial |
P92637
|
FINISHED |
| Object | metal |
—
|
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: metal | Statement: [Junkers J 1, controlSurfacesMaterial, metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSurfacesMaterial Context triple: [Junkers J 1, controlSurfacesMaterial, metal]
-
A.
controlSurfaces
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.
materialOptions
chosen
Indicates that there are one or more possible materials that can be chosen or applied in relation to a given entity or context.
-
C.
materialParameter
Indicates a relationship where a specific parameter or property is associated with, or characterizes, a material in a given context.
-
D.
materialEffect
Indicates that one material causes, influences, or brings about a change in the properties, behavior, or state of another material or system.
-
E.
materialCompatibility
Indicates that two or more materials are suitable to be used together without causing adverse interactions, degradation, or performance issues.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:49 p.m.