Triple
T37743653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceylon Workers Congress |
E940787
|
entity |
| Predicate | sectoralBase |
P78681
|
FINISHED |
| Object | plantation sector |
—
|
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: plantation sector | Statement: [Ceylon Workers Congress, sectoralBase, plantation sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectoralBase Context triple: [Ceylon Workers Congress, sectoralBase, plantation sector]
-
A.
sectoralExample
Indicates that something serves as a representative or illustrative example within a particular sector or industry context.
-
B.
sectorBase
chosen
Indicates that one entity serves as the primary base or foundational location for operations within a particular sector of another entity.
-
C.
sectoralClassification
Indicates how an entity is categorized into a specific economic or industry sector within a classification scheme.
-
D.
sectoralVariation
Indicates differences or changes that occur across distinct sectors, fields, or domains within a broader system or context.
-
E.
sectoralCoverage
Indicates the specific sectors, industries, or domains to which something (such as a policy, agreement, or dataset) applies or extends.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.