Triple
T3769330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Selection – Competition |
E82757
|
entity |
| Predicate | awardDecisionBy |
P10475
|
FINISHED |
| Object | international jury |
—
|
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: international jury | Statement: [Official Selection – Competition, awardDecisionBy, international jury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardDecisionBy Context triple: [Official Selection – Competition, awardDecisionBy, international jury]
-
A.
awardSelectionBy
chosen
Indicates that an award or honor was chosen or determined by a particular person, group, or organization.
-
B.
awardStatus
Indicates the current state or outcome of an award in relation to an entity, such as whether it has been granted, pending, rejected, or completed.
-
C.
awardTo
Indicates that an award, prize, or honor is given or assigned to a particular recipient.
-
D.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
E.
awardSystem
Indicates a relationship where an entity establishes or uses a structured scheme for granting awards, honors, or recognitions to others.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.