Triple
T29664887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humble Pie |
E750499
|
entity |
| Predicate | notableLiveReputation |
—
|
GENERATED |
| Object | high-energy concerts |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLiveReputation Context triple: [Humble Pie, notableLiveReputation, high-energy concerts]
-
A.
liveReputation
chosen
Indicates a dynamic, continuously updated assessment of an entity’s standing, trustworthiness, or performance based on recent or real-time information.
-
B.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
C.
notableOnlinePresence
Indicates that an entity maintains a significant, recognizable, or influential presence in online platforms or digital media.
-
D.
reputationHub
Indicates a central entity that aggregates, manages, or influences the reputations of multiple other entities.
-
E.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
- F. None of above.
Provenance (1 batch)
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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7 p.m.