Triple
T35499512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDIMET |
E1025959
|
entity |
| Predicate | processingRoute |
P183360
|
FINISHED |
| Object | wrought |
—
|
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: wrought | Statement: [UDIMET, processingRoute, wrought]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingRoute Context triple: [UDIMET, processingRoute, wrought]
-
A.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
-
B.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
C.
processingActivity
Indicates that one entity performs or undergoes a specific operation or series of operations applied to another entity or its data.
-
D.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
E.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.