Triple
T1157145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potosí |
E24407
|
entity |
| Predicate | associatedWithLaborSystem |
P3027
|
FINISHED |
| Object | mita |
—
|
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: mita | Statement: [Potosí, associatedWithLaborSystem, mita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLaborSystem Context triple: [Potosí, associatedWithLaborSystem, mita]
-
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.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
C.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
D.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
E.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc92ae008190a587c12ecc9a502a |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.