Triple
T35602943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maintenance Domain |
E1028803
|
entity |
| Predicate | mayBeType |
P14124
|
FINISHED |
| Object | customer Maintenance Domain |
—
|
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: customer Maintenance Domain | Statement: [Maintenance Domain, mayBeType, customer Maintenance Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeType Context triple: [Maintenance Domain, mayBeType, customer Maintenance Domain]
-
A.
mayBeDeclared
Indicates that something has the potential or permission to be formally stated, specified, or announced, but has not necessarily been declared yet.
-
B.
canBeTypeOf
chosen
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
C.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
D.
mayBeExtended
Indicates that something has the potential or option to be lengthened in duration, scope, or size beyond its current or initial limits.
-
E.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.