Triple
T27736362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.MemberInfo |
E697538
|
entity |
| Predicate | memberTypesCovered |
P121
|
FINISHED |
| Object | method |
—
|
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: method | Statement: [System.Reflection.MemberInfo, memberTypesCovered, method]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberTypesCovered Context triple: [System.Reflection.MemberInfo, memberTypesCovered, method]
-
A.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
B.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
C.
tiersCovered
Indicates that certain predefined levels, categories, or tiers are included or provided under a given arrangement or context.
-
D.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
E.
membershipPropertiesAre
Indicates that specific properties or attributes are associated with, or required for, a particular membership.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 3:12 p.m.