Triple
T35499481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDIMET |
E1025959
|
entity |
| Predicate | notableGrade |
P207010
|
FINISHED |
| Object | UDIMET 500 |
E1025959
|
NE 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: UDIMET 500 | Statement: [UDIMET, notableGrade, UDIMET 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGrade Context triple: [UDIMET, notableGrade, UDIMET 500]
-
A.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
B.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
-
C.
notableRank
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
D.
notableLevelType
Indicates that one entity is recognized as a notable or distinguished type or category of the other entity.
-
E.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
- F. None of above. chosen
Provenance (5 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38404c35348190b0609879bff896c0 |
completed | June 21, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.