Triple
T15971517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jens Grede |
E387333
|
entity |
| Predicate | businessReputation |
P83581
|
FINISHED |
| Object | high-profile brand builder |
—
|
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-profile brand builder | Statement: [Jens Grede, businessReputation, high-profile brand builder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessReputation Context triple: [Jens Grede, businessReputation, high-profile brand builder]
-
A.
commercialReputation
chosen
Indicates the perceived standing or esteem of an entity in a commercial or business context, based on others’ experiences, opinions, or evaluations.
-
B.
performanceReputation
Indicates the perceived quality or reliability of an entity’s past or expected performance as judged by others.
-
C.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
-
D.
institutionalReputationContext
Indicates the situational or environmental factors that shape or influence an institution’s reputation.
-
E.
internationalReputation
Indicates the recognized standing, esteem, or status an entity holds within the global or international community.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.