Triple
T26777869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beanpot Hall of Fame |
E670166
|
entity |
| Predicate | competitionRecognized |
P166629
|
FINISHED |
| Object | Beanpot |
—
|
NE NERFINISHED |
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: Beanpot | Statement: [Beanpot Hall of Fame, competitionRecognized, Beanpot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionRecognized Context triple: [Beanpot Hall of Fame, competitionRecognized, Beanpot]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitiveDiscipline
Indicates a relationship where an entity participates in or is associated with a structured, rule-based activity or field in which individuals or groups compete against each other.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
competitiveCategory
Indicates that two entities belong to the same market or activity segment in which they compete with one another.
-
E.
competitionRenamedAs
Indicates that a competition previously known by one name is now officially referred to by a different name.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 4:06 a.m.