Triple
T18366363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial |
E440055
|
entity |
| Predicate | primarySectorServed |
P101656
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Imperial, primarySectorServed, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySectorServed Context triple: [Imperial, primarySectorServed, agriculture]
-
A.
primarySectorCoverage
Indicates that one entity serves as the main or dominant sector in which another entity operates, focuses, or provides coverage.
-
B.
primarySectorActivity
chosen
Indicates the main industry or sector in which an entity primarily conducts its activities or operations.
-
C.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
D.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
E.
servesIndustrialRegion
Indicates that an entity provides services or support to an industrial region, fulfilling functional or operational needs of that area.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174e834481909453ba25561d1b1d |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.