Triple
T34141528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP over ATM |
E875730
|
entity |
| Predicate | encapsulationMethod |
P859
|
FINISHED |
| Object | VC-multiplexed |
—
|
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: VC-multiplexed | Statement: [PPP over ATM, encapsulationMethod, VC-multiplexed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encapsulationMethod Context triple: [PPP over ATM, encapsulationMethod, VC-multiplexed]
-
A.
encapsulation
Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
-
B.
encapsulatesValue
Indicates that one entity contains and represents the underlying value of another entity as its internal content.
-
C.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
E.
encapsulationDirection
Indicates the direction in which one entity encloses, contains, or wraps around another within an encapsulation relationship.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.