Triple
T27736367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.MemberInfo |
E697538
|
entity |
| Predicate | commonDerivedType |
P182220
|
FINISHED |
| Object | System.Reflection.MethodInfo |
—
|
NE NERFINISHED |
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.MethodInfo | Statement: [System.Reflection.MemberInfo, commonDerivedType, System.Reflection.MethodInfo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonDerivedType Context triple: [System.Reflection.MemberInfo, commonDerivedType, System.Reflection.MethodInfo]
-
A.
commonEltype
Indicates that multiple entities share the same underlying element type.
-
B.
derivationType
Indicates the specific manner or process by which one entity is derived or obtained from another.
-
C.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
-
E.
commonBasis
Indicates that two or more entities share an underlying foundation, principle, or set of assumptions that supports or explains their relationship.
- F. None of above. chosen
Provenance (4 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 27, 2026, 3:12 p.m.