Triple
T108025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Colonies |
E2180
|
entity |
| Predicate | laborSystems |
P3027
|
FINISHED |
| Object | free 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: free labor | Statement: [Middle Colonies, laborSystems, free labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborSystems Context triple: [Middle Colonies, laborSystems, free labor]
-
A.
laborSystem
chosen
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
-
B.
laborRelationsIssue
Indicates a relationship where there is a dispute, concern, or matter involving labor relations between workers (or their representatives) and employers.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
E.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25a1199ac8190ac65ffaaf45b4f5b |
completed | Feb. 28, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69a2563e7188819091e9a94e071991d7 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.