Triple
T38667498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Seattle mayoral election |
E940491
|
entity |
| Predicate | primaryTopFinisher |
P104052
|
FINISHED |
| Object | Joe Mallahan |
E2289078
|
NE 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: Joe Mallahan | Statement: [2009 Seattle mayoral election, primaryTopFinisher, Joe Mallahan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTopFinisher Context triple: [2009 Seattle mayoral election, primaryTopFinisher, Joe Mallahan]
-
A.
formerTopPrize
Indicates that an entity once held the highest or most prestigious prize or award in a given context, but no longer does.
-
B.
bestRaceFinish
Indicates the highest (best) finishing position an entity has achieved in a race.
-
C.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
D.
firstRunningWinner
Indicates that the subject is the first entity to win among those participating in a running event or race.
-
E.
topper
chosen
Indicates that one entity is the highest-ranking or best-performing among a set, often in a competitive or comparative context.
- F. None of above.
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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5b063a075081909a71d643f6b858a2 |
completed | July 18, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.