Triple
T29501317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL M‑18BS Dromader |
E748374
|
entity |
| Predicate | primaryUserSector |
P143750
|
FINISHED |
| Object | agricultural operators |
—
|
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: agricultural operators | Statement: [PZL M‑18BS Dromader, primaryUserSector, agricultural operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserSector Context triple: [PZL M‑18BS Dromader, primaryUserSector, agricultural operators]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
typicalConstituentSector
Indicates that something is a usual or characteristic sector that forms part of a larger whole or system.
-
C.
professionalSector
Indicates the industry or field in which an entity conducts its professional or occupational activities.
-
D.
primaryBusinessArea
Indicates the main field, sector, or domain in which an entity primarily conducts its business activities.
-
E.
economicSectors
chosen
Indicates a relationship that associates entities with the economic sectors or industries in which they operate or to which they belong.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a013b78bde881909a082beced4e0157 |
completed | May 11, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a013acf45508190a999b208066072bd |
completed | May 11, 2026, 2:11 a.m. |
Created at: April 28, 2026, 4:23 p.m.