Triple
T5839068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of cassation |
E129546
|
entity |
| Predicate | mayBeOrganizedBy |
P67489
|
FINISHED |
| Object | chambers |
—
|
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: chambers | Statement: [court of cassation, mayBeOrganizedBy, chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeOrganizedBy Context triple: [court of cassation, mayBeOrganizedBy, chambers]
-
A.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
B.
notOrganizedBy
Indicates that an event, activity, or entity is explicitly not arranged, coordinated, or managed by a specified agent or organization.
-
C.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
D.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
E.
formerlyOrganisedBy
Indicates that an event or activity was organized by a particular entity in the past, but is no longer organized by that 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:54 p.m.