Triple
T30132052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PATCO strike |
E765870
|
entity |
| Predicate | numberOfWorkersFired |
P202063
|
FINISHED |
| Object | over 11000 |
—
|
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: over 11000 | Statement: [PATCO strike, numberOfWorkersFired, over 11000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWorkersFired Context triple: [PATCO strike, numberOfWorkersFired, over 11000]
-
A.
firedFrom
Indicates that an entity has been dismissed or terminated from a position, job, or role by another entity.
-
B.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
C.
numberOfFirefightersInvolved
Indicates the total count of firefighters who participated in or were involved in a specific event, incident, or operation.
-
D.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
E.
numberOfMembersLeaving
Indicates the quantity of members that are departing or have departed from a group or organization.
- F. None of above. chosen
Provenance (4 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_6a004b69d8788190965dcf3653ac88a9 |
completed | May 10, 2026, 9:10 a.m. |
Created at: April 29, 2026, 7:15 p.m.