Triple
T16600261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Postal Workers |
E403311
|
entity |
| Predicate | laborHistoryEventParticipation |
P66992
|
FINISHED |
| Object | 1970USPostalStrike |
—
|
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: 1970USPostalStrike | Statement: [American Postal Workers, laborHistoryEventParticipation, 1970USPostalStrike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborHistoryEventParticipation Context triple: [American Postal Workers, laborHistoryEventParticipation, 1970USPostalStrike]
-
A.
historicalEventParticipation
chosen
Indicates that an entity took part in, contributed to, or was involved in a specific historical event.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
D.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
E.
historicalOccupationPattern
Indicates a recurring or characteristic pattern in the occupations held by an entity or its members over historical periods.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.