Triple
T2590766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSI physical layer |
E58114
|
entity |
| Predicate | examplesInclude |
P1393
|
FINISHED |
| Object | Ethernet physical layer standards |
—
|
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: Ethernet physical layer standards | Statement: [OSI physical layer, examplesInclude, Ethernet physical layer standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examplesInclude Context triple: [OSI physical layer, examplesInclude, Ethernet physical layer standards]
-
A.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
-
D.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
-
E.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd40075f08190b760cb41c1417169 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.