Triple
T24771425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miner’s Memorial and Immigrant Park |
E619732
|
entity |
| Predicate | hasTypeOfWorkersHonored |
P158670
|
FINISHED |
| Object | immigrant laborers |
—
|
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: immigrant laborers | Statement: [Miner’s Memorial and Immigrant Park, hasTypeOfWorkersHonored, immigrant laborers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWorkersHonored Context triple: [Miner’s Memorial and Immigrant Park, hasTypeOfWorkersHonored, immigrant laborers]
-
A.
hasTypeOfWorkersHonored
chosen
Indicates that a subject recognizes or celebrates a particular category or type of workers.
-
B.
hasWorker
Indicates that one entity employs, utilizes, or is associated with another entity in the role of a worker.
-
C.
hasWorkRecognizedBy
Indicates that one entity’s work, creation, or contribution has been formally acknowledged, honored, or cited by another entity.
-
D.
hasWorkRecognized
Indicates that an entity’s work, contribution, or achievement has been formally acknowledged or honored by another entity or authority.
-
E.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 4:31 a.m.