Triple
T29229176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittston Coal Company |
E741019
|
entity |
| Predicate | laborDisputeEnd |
P150608
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Pittston Coal Company, laborDisputeEnd, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborDisputeEnd Context triple: [Pittston Coal Company, laborDisputeEnd, 1990]
-
A.
disputeResolvedIn
Indicates that a particular dispute has been settled or resolved within a specified location, forum, or jurisdiction.
-
B.
disputeEndTime
chosen
Indicates the point in time at which a dispute is considered resolved or officially concluded.
-
C.
disputeResolvedBy
Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
-
D.
resolvedDisputeOver
Indicates that one entity successfully settled or brought to an end a conflict, disagreement, or contention concerning another entity.
-
E.
laborRelationsIssue
Indicates a relationship where there is a dispute, concern, or matter involving labor relations between workers (or their representatives) and employers.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 12:18 p.m.