Triple
T30357610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD series |
E772189
|
entity |
| Predicate | serviceability |
P182414
|
FINISHED |
| Object | repairable by specialists |
—
|
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: repairable by specialists | Statement: [DD series, serviceability, repairable by specialists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceability Context triple: [DD series, serviceability, repairable by specialists]
-
A.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
B.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
C.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
D.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 29, 2026, 7:57 p.m.