Triple
T10159013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFnet |
E233840
|
entity |
| Predicate | hasNotableChannel |
P45103
|
FINISHED |
| Object | #irchelp |
—
|
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: #irchelp | Statement: [EFnet, hasNotableChannel, #irchelp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChannel Context triple: [EFnet, hasNotableChannel, #irchelp]
-
A.
notableChannel
chosen
Indicates that a channel is recognized as particularly significant, prominent, or noteworthy in some context.
-
B.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
C.
hasNotableNetwork
Indicates that one entity is recognized for having a significant, influential, or widely connected network or set of relationships with other entities.
-
D.
hasNotableStation
Indicates that an entity possesses or is associated with a station that is considered notable or significant in some context.
-
E.
hasSpecialtyChannel
Indicates that one entity provides or is associated with a dedicated channel focused on a particular specialty or subject area for 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.