Triple
T19289685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhadohi |
E482406
|
entity |
| Predicate | hasSectoralSpecialization |
P20603
|
FINISHED |
| Object | floor coverings |
—
|
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: floor coverings | Statement: [Bhadohi, hasSectoralSpecialization, floor coverings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectoralSpecialization Context triple: [Bhadohi, hasSectoralSpecialization, floor coverings]
-
A.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
B.
hasSectoralPriority
Indicates that something is designated as having priority or special importance within a particular sector or industry.
-
C.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
-
D.
hasIndustrialSector
chosen
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
E.
hasOccupationSector
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc050a888190ac204d1e736200c5 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.