Triple
T17141664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Focke-Wulf Ta 183 design |
E415978
|
entity |
| Predicate | projectedUse |
P12134
|
FINISHED |
| Object | Luftwaffe fighter replacement |
—
|
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: Luftwaffe fighter replacement | Statement: [Focke-Wulf Ta 183 design, projectedUse, Luftwaffe fighter replacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectedUse Context triple: [Focke-Wulf Ta 183 design, projectedUse, Luftwaffe fighter replacement]
-
A.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
-
C.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
-
D.
forecastUsing
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.