Triple
T1115359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscar |
E11086
|
entity |
| Predicate | selectionStage |
P2703
|
FINISHED |
| Object | nominations |
—
|
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: nominations | Statement: [Oscar, selectionStage, nominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionStage Context triple: [Oscar, selectionStage, nominations]
-
A.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
B.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
E.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.