Triple
T13592999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngöbe |
E324738
|
entity |
| Predicate | commonEmployment |
P110208
|
FINISHED |
| Object | agricultural wage labor |
—
|
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: agricultural wage labor | Statement: [Ngöbe, commonEmployment, agricultural wage labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonEmployment Context triple: [Ngöbe, commonEmployment, agricultural wage labor]
-
A.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
B.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
C.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
D.
peakEmployment
Indicates that an entity has reached its highest level of employment or workforce size during a specified period.
-
E.
employment
Indicates a relationship where one entity hires, contracts, or otherwise engages another to perform work or services, typically in exchange for compensation.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.