Triple
T1612276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident |
E34638
|
entity |
| Predicate | vendorPrefix |
P7276
|
FINISHED |
| Object | -ms- |
—
|
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: -ms- | Statement: [Trident, vendorPrefix, -ms-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorPrefix Context triple: [Trident, vendorPrefix, -ms-]
-
A.
vendorSpecificTo
Indicates that something is tailored, restricted, or applicable only to a particular vendor or supplier, and not generally applicable across others.
-
B.
standardPrefix
chosen
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
C.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
D.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
E.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.