Triple
T38369985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmontown |
E892550
|
entity |
| Predicate | frequentPerformer |
P83286
|
FINISHED |
| Object | Spencer Crittenden |
—
|
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: Spencer Crittenden | Statement: [Harmontown, frequentPerformer, Spencer Crittenden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentPerformer Context triple: [Harmontown, frequentPerformer, Spencer Crittenden]
-
A.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
-
B.
frequentPatron
Indicates that one entity regularly and repeatedly visits, uses, or patronizes another entity (such as a place, service, or establishment).
-
C.
frequentlyFeaturesPerformer
chosen
Indicates that a subject (such as a work, series, or venue) regularly includes or showcases a particular performer more often than others.
-
D.
frequentExhibitor
Indicates that an entity regularly or repeatedly participates as an exhibitor in events, shows, or exhibitions.
-
E.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.