Triple
T27736876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.AssemblyKeyNameAttribute |
E697549
|
entity |
| Predicate | parameterName |
P14546
|
FINISHED |
| Object | keyName |
—
|
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: keyName | Statement: [System.Reflection.AssemblyKeyNameAttribute, parameterName, keyName]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterName Context triple: [System.Reflection.AssemblyKeyNameAttribute, parameterName, keyName]
-
A.
parameter
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
payloadName
Indicates the specific name assigned to a payload associated with an action, event, or data transfer between entities.
-
C.
genericParameter
Indicates that one entity functions as a type or template parameter that is supplied to or constrained by another entity.
-
D.
parametrizes
Indicates that one entity defines or controls the variable parameters that determine the behavior, form, or configuration of another entity.
-
E.
fieldName
chosen
Indicates the specific name or label assigned to a field within a data structure, form, or record.
- 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_69f636a161608190b0cdf03863204034 |
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:13 p.m.