Triple
T1407659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted 3 (announced) |
E31730
|
entity |
| Predicate | ratingExpectation |
P27677
|
FINISHED |
| Object | R (anticipated) |
—
|
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: R (anticipated) | Statement: [Ted 3 (announced), ratingExpectation, R (anticipated)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratingExpectation Context triple: [Ted 3 (announced), ratingExpectation, R (anticipated)]
-
A.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
B.
ratingSystem
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
C.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
D.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
E.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bf7f0c8190aee96818de6ff4a5 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.