Triple
T6953637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD 5.1 |
E161187
|
entity |
| Predicate | channelSeparation |
P34891
|
FINISHED |
| Object | discrete channels |
—
|
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: discrete channels | Statement: [DD 5.1, channelSeparation, discrete channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelSeparation Context triple: [DD 5.1, channelSeparation, discrete channels]
-
A.
channelSeparatingFrom
Indicates that one channel is moving away or becoming detached from another channel or boundary.
-
B.
usesSeparateChannelFor
chosen
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
C.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
D.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
E.
separatesDirection
Indicates that one entity divides or distinguishes different directions or directional paths from each other.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.