Triple
T29664887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humble Pie |
E750499
|
entity |
| Predicate | notableLiveReputation |
P60235
|
FINISHED |
| Object | high-energy concerts |
—
|
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: high-energy concerts | Statement: [Humble Pie, notableLiveReputation, high-energy concerts]
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 (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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7 p.m.