Triple
T11505103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossbench |
E272762
|
entity |
| Predicate | roleOfConvenor |
P39086
|
FINISHED |
| Object | coordinates Crossbench business |
—
|
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: coordinates Crossbench business | Statement: [Crossbench, roleOfConvenor, coordinates Crossbench business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfConvenor Context triple: [Crossbench, roleOfConvenor, coordinates Crossbench business]
-
A.
convenesAs
chosen
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
-
B.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
C.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
D.
co-organizerOf
Indicates that an entity shares responsibility with others in planning, coordinating, or managing an event, project, or activity.
-
E.
convenedFor
Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db2f4b08190801de1b773932f59 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.