Triple
T36934269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audience Award |
E913569
|
entity |
| Predicate | mayBeGivenFor |
P12882
|
FINISHED |
| Object | feature film |
—
|
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: feature film | Statement: [Audience Award, mayBeGivenFor, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeGivenFor Context triple: [Audience Award, mayBeGivenFor, feature film]
-
A.
mayBeGivenTo
Indicates that something is permitted or eligible to be transferred, assigned, or provided from one entity to another.
-
B.
mayProvideFor
Indicates that one entity is permitted or has the option to supply, support, or otherwise furnish something for another entity.
-
C.
mayAlsoBeProvidedAs
Indicates that something can optionally be supplied or made available in an alternative form or manner in addition to its primary provision.
-
D.
givenFor
chosen
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
E.
canGive
Indicates that one entity has the ability or permission to transfer something to another entity.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.