Triple
T30611597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midi-job |
E779192
|
entity |
| Predicate | hasStartOfEarningsRange |
P196904
|
FINISHED |
| Object | above mini-job earnings threshold |
—
|
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: above mini-job earnings threshold | Statement: [Midi-job, hasStartOfEarningsRange, above mini-job earnings threshold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartOfEarningsRange Context triple: [Midi-job, hasStartOfEarningsRange, above mini-job earnings threshold]
-
A.
hasEndOfEarningsRange
Indicates that an entity’s earnings are bounded above by a specified maximum value in a defined range.
-
B.
earningsStatus
Indicates the current state or condition of an entity’s earnings, such as whether they are realized, projected, stable, increasing, or decreasing.
-
C.
hasEmployeeRange
Indicates the range or limits on the number of employees associated with an entity.
-
D.
hasInceptionPeriod
Indicates the time span or period during which something begins or comes into existence.
-
E.
appearsInWorkRange
Indicates that an entity is featured or occurs within a specified range or subset of a larger work or collection of works.
- 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_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: April 29, 2026, 8:26 p.m.