Triple
T31269339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balak |
E797339
|
entity |
| Predicate | attemptedToHire |
P75129
|
FINISHED |
| Object | Balaam |
—
|
NE NERFINISHED |
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: Balaam | Statement: [Balak, attemptedToHire, Balaam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedToHire Context triple: [Balak, attemptedToHire, Balaam]
-
A.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
employmentAction
chosen
Indicates an action or event that changes, initiates, or terminates an employment relationship between entities.
-
C.
appliedFor
Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
-
D.
ResumeStatus
Indicates the current state or condition of a resume within a review or processing workflow.
-
E.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
- F. None of above.
Provenance (3 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:13 p.m.