Triple
T23139588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois park district |
E577422
|
entity |
| Predicate | canEmploy |
P58475
|
FINISHED |
| Object | park professionals |
—
|
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: park professionals | Statement: [Illinois park district, canEmploy, park professionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEmploy Context triple: [Illinois park district, canEmploy, park professionals]
-
A.
canHire
chosen
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure of another entity.
-
C.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
D.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
E.
commonEmployment
Indicates that two or more entities share the same employer or have worked for the same organization.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8e23988190814524f63a7efe36 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.