Triple
T10330141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMS |
E242851
|
entity |
| Predicate | capabilitiesDocumentFormat |
P23225
|
FINISHED |
| Object | XML |
—
|
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: XML | Statement: [WMS, capabilitiesDocumentFormat, XML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capabilitiesDocumentFormat Context triple: [WMS, capabilitiesDocumentFormat, XML]
-
A.
featuresFormat
chosen
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
B.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
formatCompatibleWith
Indicates that one format can be correctly used, interpreted, or processed in conjunction with another format without conflict or loss of information.
-
D.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
E.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.