Triple
T20141319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Man |
E491171
|
entity |
| Predicate | reputationDescriptor |
P78687
|
FINISHED |
| Object | low-profile mob boss |
—
|
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: low-profile mob boss | Statement: [The Old Man, reputationDescriptor, low-profile mob boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputationDescriptor Context triple: [The Old Man, reputationDescriptor, low-profile mob boss]
-
A.
denotesReputationOf
chosen
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
-
B.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
C.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
D.
reputationInSources
Indicates that an entity has a certain reputation or standing as reflected or reported in various information sources.
-
E.
refersToPersonReputation
Indicates that something is about, concerns, or makes reference to a particular person's reputation.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679b179c8190a9511df8ed82098a |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.