Triple
T9527683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen & Overy Prize for Law and Economics |
E229801
|
entity |
| Predicate | mayBeSharedBy |
P2507
|
FINISHED |
| Object | multiple recipients |
—
|
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: multiple recipients | Statement: [Allen & Overy Prize for Law and Economics, mayBeSharedBy, multiple recipients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeSharedBy Context triple: [Allen & Overy Prize for Law and Economics, mayBeSharedBy, multiple recipients]
-
A.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
B.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
C.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
notSharedWith
Indicates that something is intentionally not disclosed, distributed, or made accessible to a specified party or set of parties.
-
E.
hasResponsibilitiesSharedWith
Indicates that two or more entities share joint responsibility for certain tasks, duties, or obligations.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b0466081908eb637e2185dea37 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.