Triple
T27733133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IEquatable`1 |
E697475
|
entity |
| Predicate | methodParameterType |
P125616
|
FINISHED |
| Object | T |
—
|
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: T | Statement: [System.IEquatable`1, methodParameterType, T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodParameterType Context triple: [System.IEquatable`1, methodParameterType, T]
-
A.
constructorParameterType
Indicates that a given parameter of a constructor has a specific data type.
-
B.
hasParameterType
chosen
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
C.
argumentType
Indicates that one entity serves as a specific semantic or syntactic argument role (such as subject, object, or complement) in relation to another entity or event.
-
D.
genericParameter
Indicates that one entity functions as a type or template parameter that is supplied to or constrained by another entity.
-
E.
hasParameter
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
- 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_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 3:12 p.m.