Triple
T31173969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralph Drowne |
E794688
|
entity |
| Predicate | reputationAfterEvent |
P56376
|
FINISHED |
| Object | renowned artist |
—
|
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: renowned artist | Statement: [Ralph Drowne, reputationAfterEvent, renowned artist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationAfterEvent Context triple: [Ralph Drowne, reputationAfterEvent, renowned artist]
-
A.
reputationEffect
Indicates how one entity’s actions or characteristics influence the perceived reputation or standing of another entity.
-
B.
laterReputation
chosen
Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
-
C.
reputationBeforeScandal
Indicates the reputation or public standing an entity had prior to a specific scandal or damaging event.
-
D.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
E.
preFireReputation
Indicates the reputation or standing an entity had before a particular fire-related event or incident occurred.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:07 p.m.