Triple
T33951999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashim BeShas |
E870463
|
entity |
| Predicate | organizationalSector |
P100108
|
FINISHED |
| Object | civil society |
—
|
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: civil society | Statement: [Nashim BeShas, organizationalSector, civil society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationalSector Context triple: [Nashim BeShas, organizationalSector, civil society]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
sectoralOrganizations
Indicates that there is an organizational relationship specifically structured around a particular sector or industry.
-
C.
sectorOfOperation
chosen
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
D.
sectorOfParentOrganization
Indicates that the specified sector or industry classification belongs to, or characterizes, the parent organization of the given entity.
-
E.
sectoralClassification
Indicates how an entity is categorized into a specific economic or industry sector within a classification scheme.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:49 a.m.