Triple
T8552379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES |
E202472
|
entity |
| Predicate | commercialReputation |
P83581
|
FINISHED |
| Object | luxury home console |
—
|
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: luxury home console | Statement: [AES, commercialReputation, luxury home console]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialReputation Context triple: [AES, commercialReputation, luxury home console]
-
A.
performanceReputation
Indicates the perceived quality or reliability of an entity’s past or expected performance as judged by others.
-
B.
institutionalReputationContext
Indicates the situational or environmental factors that shape or influence an institution’s reputation.
-
C.
manufacturerReputation
Indicates the perceived reliability, quality, and trustworthiness associated with a product’s manufacturer.
-
D.
internationalReputation
Indicates the recognized standing, esteem, or status an entity holds within the global or international community.
-
E.
reputationBuiltFor
Indicates that one entity has established or developed a reputation specifically for or in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8882704819094b688d46169433a |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.