Triple
T5992419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Loman |
E133381
|
entity |
| Predicate | workBehavior |
P67882
|
FINISHED |
| Object | exaggerates professional success |
—
|
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: exaggerates professional success | Statement: [Happy Loman, workBehavior, exaggerates professional success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workBehavior Context triple: [Happy Loman, workBehavior, exaggerates professional success]
-
A.
workMode
Indicates the manner, configuration, or operational state in which an entity performs its work or function.
-
B.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
C.
workPattern
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
D.
workBecame
Indicates that one work was transformed, adapted, or evolved into another work over time.
-
E.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.