Triple
T15044401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welfare Officer |
E379185
|
entity |
| Predicate | mayOrganise |
P67489
|
FINISHED |
| Object | wellbeing events |
—
|
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: wellbeing events | Statement: [Welfare Officer, mayOrganise, wellbeing events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOrganise Context triple: [Welfare Officer, mayOrganise, wellbeing events]
-
A.
mayAttend
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
-
B.
mayBeOrganizedBy
chosen
Indicates that an event, activity, or entity has the possibility of being organized or arranged by a particular agent or organization, without asserting that this organization definitely occurs.
-
C.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
D.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
E.
mayCompose
Indicates that an entity has permission or authority to create or write another entity (such as a document, message, or composition).
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded830c3c08190a87b81abbbb75377 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.