Triple
T17716415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelly Levene |
E442210
|
entity |
| Predicate | pastReputation |
P93104
|
FINISHED |
| Object | top salesman |
—
|
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: top salesman | Statement: [Shelly Levene, pastReputation, top salesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastReputation Context triple: [Shelly Levene, pastReputation, top salesman]
-
A.
laterReputation
Indicates that an entity’s reputation or status at a later time is being referred to in relation to an earlier point or context.
-
B.
haveReputation
chosen
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
C.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
D.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
E.
reputationBefore1969
Indicates that one entity had a particular reputation or standing in relation to another entity prior to the year 1969.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47480955481908fa0d3d34aaedd48 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.