Triple
T9541079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASTOR |
E230157
|
entity |
| Predicate | dataLinkType |
P1378
|
FINISHED |
| Object | secure data link |
—
|
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: secure data link | Statement: [ASTOR, dataLinkType, secure data link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLinkType Context triple: [ASTOR, dataLinkType, secure data link]
-
A.
linkLayer
chosen
Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
-
B.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
C.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
D.
interconnectionType
Indicates the specific kind or nature of relationship that links two or more entities together.
-
E.
dataPlaneType
Indicates the type or category of data plane through which data traffic or operations are carried out in a system or network.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.