Triple
T11061761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Development Council VIII |
E261523
|
entity |
| Predicate | sectoralCoverage |
P97586
|
FINISHED |
| Object | multi-sectoral |
—
|
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: multi-sectoral | Statement: [Regional Development Council VIII, sectoralCoverage, multi-sectoral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectoralCoverage Context triple: [Regional Development Council VIII, sectoralCoverage, multi-sectoral]
-
A.
primarySectorCoverage
Indicates that one entity serves as the main or dominant sector in which another entity operates, focuses, or provides coverage.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
sectorInfluence
Indicates the degree to which one sector affects, shapes, or exerts control over another sector or over outcomes within that sector.
-
D.
notableSector
Indicates that an entity is particularly prominent, influential, or significant within a specified sector or industry.
-
E.
targetsSector
Indicates that an entity is directed toward, focused on, or intended to affect a particular economic or industry sector.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798ea834c819099401e69f995c59f |
completed | April 9, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.