Triple
T16747070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | encapsulatesInformationAbout |
P86949
|
FINISHED |
| Object | destination protocol or service |
—
|
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: destination protocol or service | Statement: [DSAP, encapsulatesInformationAbout, destination protocol or service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encapsulatesInformationAbout Context triple: [DSAP, encapsulatesInformationAbout, destination protocol or service]
-
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.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
C.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
D.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
E.
typeOfInformation
Indicates that one entity specifies the category or kind of information that characterizes or describes 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.