Triple
T25026316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Excellence Award |
E626718
|
entity |
| Predicate | selectionProcessMayInclude |
P126
|
FINISHED |
| Object | customer feedback |
—
|
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 feedback | Statement: [Service Excellence Award, selectionProcessMayInclude, customer feedback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionProcessMayInclude Context triple: [Service Excellence Award, selectionProcessMayInclude, customer feedback]
-
A.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
B.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
C.
selectionProcessAbbreviation
Indicates that one entity is an abbreviation or shortened form used to refer to a particular selection process.
-
D.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
E.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:07 a.m.