Triple
T10330101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMS |
E242851
|
entity |
| Predicate | supportsMultipleLayersPerRequest |
P93451
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WMS, supportsMultipleLayersPerRequest, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleLayersPerRequest Context triple: [WMS, supportsMultipleLayersPerRequest, true]
-
A.
supportsLayeredDivisionMultiplexing
Indicates that one entity enables or is compatible with the use of layered division multiplexing techniques in conjunction with another entity.
-
B.
supportsLayerHierarchy
Indicates that one element can contain and organize other elements within a structured, ordered layer system.
-
C.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
D.
supportsMultipleRanges
Indicates that an entity can handle, accept, or operate over more than one distinct range of values or intervals.
-
E.
supportsMultipleOnSameTarget
Indicates that the relationship or action can be applied multiple times concurrently to the same target entity.
- 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_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. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.