Triple
T6784975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finalist Alliance Award |
E155777
|
entity |
| Predicate | positionRecognized |
P72986
|
FINISHED |
| Object | runner-up |
—
|
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: runner-up | Statement: [Finalist Alliance Award, positionRecognized, runner-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRecognized Context triple: [Finalist Alliance Award, positionRecognized, runner-up]
-
A.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
D.
positionEstablishedFor
Indicates that a specific role or job position has been formally created or set up for a particular entity or purpose.
-
E.
positionObtainedBy
Indicates that a particular position or role is acquired, achieved, or secured through a specified action, process, or agent.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28de0348190998751fd546bfd02 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:14 p.m.