Triple
T27735435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CancellationTokenSource |
E697516
|
entity |
| Predicate | canLink |
P107489
|
FINISHED |
| Object | multiple CancellationToken instances |
—
|
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: multiple CancellationToken instances | Statement: [CancellationTokenSource, canLink, multiple CancellationToken instances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canLink Context triple: [CancellationTokenSource, canLink, multiple CancellationToken instances]
-
A.
canBeLinkedTo
chosen
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
B.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
C.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
-
D.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
E.
canBondWith
Indicates that one entity has the capability or compatibility to form a bond or connection with 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f636a088b8819081e34d416b28cdac |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.