Triple
T37902908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL P.24 (test installations) |
E945465
|
entity |
| Predicate | testEngineCountryOfOrigin |
P126219
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [PZL P.24 (test installations), testEngineCountryOfOrigin, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testEngineCountryOfOrigin Context triple: [PZL P.24 (test installations), testEngineCountryOfOrigin, United Kingdom]
-
A.
engineOriginCountry
chosen
Indicates the country where an engine was originally designed, manufactured, or first produced.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
testedEngine
Indicates that an engine has undergone a testing process to evaluate its performance, functionality, or reliability.
-
D.
testedInCountry
Indicates that an entity has been tested or evaluated within the geographical boundaries or jurisdiction of a specified country.
-
E.
originatesFromEngine
Indicates that something has its source, cause, or production in a particular engine.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.