Triple
T24650045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trojan 200 |
E610221
|
entity |
| Predicate | licenceBuiltVersionOf |
P151633
|
FINISHED |
| Object | Heinkel Kabine 200 |
—
|
NE NERFINISHED |
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: Heinkel Kabine 200 | Statement: [Trojan 200, licenceBuiltVersionOf, Heinkel Kabine 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenceBuiltVersionOf Context triple: [Trojan 200, licenceBuiltVersionOf, Heinkel Kabine 200]
-
A.
licenceBuiltFrom
Indicates that a licence is derived from, based on, or constructed using another underlying licence or licensing framework.
-
B.
licenseBuiltAs
Indicates that one entity is constructed, configured, or deployed under the terms or identity of another entity’s license.
-
C.
licenceVersion
chosen
Indicates the specific version of a licence under which something is granted, used, or distributed.
-
D.
licenseBuiltBy
Indicates that a license was created, issued, or constructed by a specific agent or organization.
-
E.
licenseBuiltFrom
Indicates that a license is derived from, or constructed based on, another underlying license or licensing template.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.