Triple
T15820455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data Link Layer |
E383592
|
entity |
| Predicate | followsLayer |
P134
|
FINISHED |
| Object | Physical Layer |
—
|
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: Physical Layer | Statement: [Data Link Layer, followsLayer, Physical Layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLayer Context triple: [Data Link Layer, followsLayer, Physical Layer]
-
A.
followsLevel
Indicates that one entity comes after or succeeds another in a defined sequence, stage, or hierarchical level.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
D.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
-
E.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a7ba4881908a2747bf063d79f1 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.