Triple
T27188012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panjgur |
E683389
|
entity |
| Predicate | dateIndustryRole |
P162240
|
FINISHED |
| Object | regional center for date trade |
—
|
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: regional center for date trade | Statement: [Panjgur, dateIndustryRole, regional center for date trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateIndustryRole Context triple: [Panjgur, dateIndustryRole, regional center for date trade]
-
A.
sectorEmploymentRole
Indicates the specific role or function an entity holds within a particular employment sector or industry.
-
B.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
C.
hasIndustryRole
Indicates that an entity holds or performs a specific role, function, or position within a particular industry or sector.
-
D.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
E.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625a9e3688190996e628a17d211d0 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:31 a.m.