Triple
T36797237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navassa Island Rebellion of 1889 |
E909215
|
entity |
| Predicate | hasLaborCondition |
P36844
|
FINISHED |
| Object | long working hours |
—
|
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: long working hours | Statement: [Navassa Island Rebellion of 1889, hasLaborCondition, long working hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaborCondition Context triple: [Navassa Island Rebellion of 1889, hasLaborCondition, long working hours]
-
A.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
B.
hasInmateLabor
Indicates that an entity utilizes or is associated with labor performed by incarcerated individuals.
-
C.
hasLaborRepresentation
Indicates that an entity is represented by a labor organization, such as a union or workers’ council, in employment-related matters.
-
D.
laborContext
chosen
Indicates the labor-related circumstances, conditions, or setting within which an action, relationship, or event takes place.
-
E.
laborSet
Indicates that a particular labor, task, or work assignment has been designated or scheduled for an entity or context.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
Created at: May 3, 2026, 4:12 p.m.