Triple
T6835431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel HeS 011 |
E157436
|
entity |
| Predicate | testingStatus |
P12388
|
FINISHED |
| Object | bench-tested |
—
|
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: bench-tested | Statement: [Heinkel HeS 011, testingStatus, bench-tested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingStatus Context triple: [Heinkel HeS 011, testingStatus, bench-tested]
-
A.
testStatus
chosen
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
B.
TestStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, is in progress, or has not yet been executed.
-
C.
testResult
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
D.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
E.
benchmarkStatus
Indicates the current evaluation state or outcome of a benchmark process applied to an entity or system.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67a9ff88190b0d86331b3ea06aa |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.