Triple
T4575463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-7 |
E123130
|
entity |
| Predicate | recommendedAlternative |
P5887
|
FINISHED |
| Object | UTF-8 with MIME quoted-printable |
—
|
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: UTF-8 with MIME quoted-printable | Statement: [UTF-7, recommendedAlternative, UTF-8 with MIME quoted-printable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedAlternative Context triple: [UTF-7, recommendedAlternative, UTF-8 with MIME quoted-printable]
-
A.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
B.
recommendedAction
Indicates that one entity suggests or prescribes a particular action for another entity to take.
-
C.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
D.
submitsRecommendationsTo
Indicates that one entity formally sends or presents recommendations to another entity for consideration or action.
-
E.
madeRecommendation
Indicates that one entity has suggested or advised another entity to consider a particular option, action, or choice.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.