Triple
T1605936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COBRA |
E34502
|
entity |
| Predicate | qualifyingEvent |
P30231
|
FINISHED |
| Object | job loss |
—
|
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: job loss | Statement: [COBRA, qualifyingEvent, job loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingEvent Context triple: [COBRA, qualifyingEvent, job loss]
-
A.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
-
B.
qualificationOrganizedBy
Indicates that a qualification (such as a course, exam, or certification) is organized or administered by a particular agent or organization.
-
C.
skillsCompetitionEvent
Indicates that a competitive event is held to assess and compare participants’ skills or abilities.
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93fa5aa04819084d1154ef900303f |
completed | March 5, 2026, 8:32 a.m. |
Created at: March 4, 2026, 7:28 p.m.