Triple
T31492589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Examination Schools |
E803446
|
entity |
| Predicate | canBeHiredFor |
P194522
|
FINISHED |
| Object | conferences |
—
|
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: conferences | Statement: [The Examination Schools, canBeHiredFor, conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHiredFor Context triple: [The Examination Schools, canBeHiredFor, conferences]
-
A.
canHire
Indicates that one entity has the authority or ability to employ or recruit another entity.
-
B.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, or context.
-
C.
canBeRecruitedFrom
Indicates that one entity is eligible to be recruited, obtained, or enlisted starting from or via another specified entity or source.
-
D.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
E.
mayWorkOn
Indicates that an entity is permitted or allowed to perform work on another entity.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
| PDg | Predicate description generation | batch_69fd783e9e5c819087dec7fefa03700d |
completed | May 8, 2026, 5:44 a.m. |
Created at: April 30, 2026, 9:39 p.m.