Triple
T30611598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midi-job |
E779192
|
entity |
| Predicate | hasEndOfEarningsRange |
P185218
|
FINISHED |
| Object | below regular full social contribution level |
—
|
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: below regular full social contribution level | Statement: [Midi-job, hasEndOfEarningsRange, below regular full social contribution level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndOfEarningsRange Context triple: [Midi-job, hasEndOfEarningsRange, below regular full social contribution level]
-
A.
endDateInBand
Indicates that the end date of an event or interval falls within a specified date range or band.
-
B.
hasEmployeeRange
Indicates the range or limits on the number of employees associated with an entity.
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
hasCollectionEndDate
Indicates the date on which a collection activity, period, or process is scheduled or recorded to end.
-
E.
hasFullRetirementAgeRange
Indicates that there is a defined span of ages during which an entity is considered to have reached full retirement status.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 29, 2026, 8:26 p.m.