Triple
T27736720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyDescriptionAttribute |
E697545
|
entity |
| Predicate | canBeReadVia |
P107394
|
FINISHED |
| Object | System.Reflection.Assembly.GetCustomAttributes |
—
|
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: System.Reflection.Assembly.GetCustomAttributes | Statement: [System.Reflection.AssemblyDescriptionAttribute, canBeReadVia, System.Reflection.Assembly.GetCustomAttributes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeReadVia Context triple: [System.Reflection.AssemblyDescriptionAttribute, canBeReadVia, System.Reflection.Assembly.GetCustomAttributes]
-
A.
canBeReadWith
chosen
Indicates that one entity is suitable or compatible to be read or interpreted together with another entity.
-
B.
canRead
Indicates that one entity has the ability or permission to read or access the content of another entity.
-
C.
canBeOpenedBy
Indicates that one entity has the ability or permission to open another entity.
-
D.
canRetrieve
Indicates that one entity has the ability or permission to retrieve or fetch another entity or resource.
-
E.
isFreeToRead
Indicates that access to the referenced content or resource does not require payment and can be read without cost.
- 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_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 3:13 p.m.