Triple
T33621126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyle McAvoy |
E861271
|
entity |
| Predicate | pressuredToWorkFor |
P176965
|
FINISHED |
| Object | large New York law firm |
—
|
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: large New York law firm | Statement: [Kyle McAvoy, pressuredToWorkFor, large New York law firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressuredToWorkFor Context triple: [Kyle McAvoy, pressuredToWorkFor, large New York law firm]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
C.
givenForWorkIn
Indicates that something (such as payment, benefit, or item) is provided to an entity specifically in exchange for or in connection with work performed in a particular role, job, or context.
-
D.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
E.
wonWork
Indicates that one party has successfully secured or been awarded a particular job, contract, or work opportunity over others.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f81b8dc48190abf63b5f5cb8538a |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.