Triple
T23927593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL |
E602399
|
entity |
| Predicate | codePlacement |
P154388
|
FINISHED |
| Object | applied to fuselage sides of RAF aircraft |
—
|
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: applied to fuselage sides of RAF aircraft | Statement: [KL, codePlacement, applied to fuselage sides of RAF aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codePlacement Context triple: [KL, codePlacement, applied to fuselage sides of RAF aircraft]
-
A.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
B.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
C.
configurationCode
Indicates that an entity is associated with a specific configuration identifier or code that defines its setup or settings.
-
D.
scriptPlacement
Indicates the spatial or contextual position where a script is located or applied relative to other elements or components.
-
E.
codeSection
Indicates a specific segment or subsection within a larger body of code that is distinguished for reference, organization, or analysis.
- F. None of above. chosen
Provenance (4 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1e13e8819096432b8133c7d71e |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:49 p.m.