Triple
T18506542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Net Promoter Score |
E452210
|
entity |
| Predicate | oftenComplementedBy |
P162
|
FINISHED |
| Object | Customer Satisfaction Score |
—
|
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: Customer Satisfaction Score | Statement: [Net Promoter Score, oftenComplementedBy, Customer Satisfaction Score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenComplementedBy Context triple: [Net Promoter Score, oftenComplementedBy, Customer Satisfaction Score]
-
A.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
B.
complements
chosen
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
C.
relatesComplementTo
Indicates that one entity serves as a complement or completing counterpart to another entity within a specified context or structure.
-
D.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
-
E.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334266708190b59aca3a2218c095 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.