Triple
T25310792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PBB |
E634601
|
entity |
| Predicate | usesEncapsulationType |
P33248
|
FINISHED |
| Object | MAC-in-MAC encapsulation |
—
|
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: MAC-in-MAC encapsulation | Statement: [PBB, usesEncapsulationType, MAC-in-MAC encapsulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEncapsulationType Context triple: [PBB, usesEncapsulationType, MAC-in-MAC encapsulation]
-
A.
encapsulation
chosen
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.
hasEnclosures
Indicates that an entity possesses or contains one or more enclosing structures, spaces, or bounded areas associated with it.
-
C.
usesHarmonyType
Indicates that one entity employs or is characterized by a particular type or system of harmony in relation to another.
-
D.
usesAbstraction
Indicates that one entity employs or relies on an abstract representation or interface of another entity rather than interacting with its concrete implementation directly.
-
E.
hasEnclosedDesign
Indicates that one entity is designed to be fully or partially enclosed within the physical or structural boundaries of another entity.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939e84dc8190bef761d9bfee08a6 |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:26 p.m.