Triple
T27946055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PredictionEngine |
E700880
|
entity |
| Predicate | discouragedUsage |
P164103
|
FINISHED |
| Object | high-scale web services |
—
|
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-scale web services | Statement: [PredictionEngine, discouragedUsage, high-scale web services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discouragedUsage Context triple: [PredictionEngine, discouragedUsage, high-scale web services]
-
A.
discouragedUsageReason
Indicates the reason why a particular usage, action, or practice is considered discouraged.
-
B.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
C.
notRecommendedIn
chosen
Indicates that something is advised against or discouraged from being used, done, or applied within a particular context, situation, or location.
-
D.
notRecommendedBy
Indicates that one entity explicitly advises against or does not endorse another entity.
-
E.
accessDiscouragedFor
Indicates that access to a particular entity is discouraged or not recommended for another entity, even if it may still be technically possible.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 7:22 p.m.