Triple
T33219009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Bannick |
E850366
|
entity |
| Predicate | publicReputation |
P78687
|
FINISHED |
| Object | respected judge |
—
|
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: respected judge | Statement: [Ross Bannick, publicReputation, respected judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicReputation Context triple: [Ross Bannick, publicReputation, respected judge]
-
A.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
B.
localReputation
Indicates the perceived standing, trustworthiness, or esteem an entity holds within a specific local community or area.
-
C.
denotesReputationOf
chosen
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
D.
peakReputation
Indicates the highest level of reputation an entity has ever attained within a given context or system.
-
E.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:30 a.m.