Triple
T27737049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.DefaultMemberAttribute |
E697553
|
entity |
| Predicate | memberNameStoredAs |
P178778
|
FINISHED |
| Object | string |
—
|
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: string | Statement: [System.Reflection.DefaultMemberAttribute, memberNameStoredAs, string]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberNameStoredAs Context triple: [System.Reflection.DefaultMemberAttribute, memberNameStoredAs, string]
-
A.
memberOriginalName
Indicates that the relationship specifies the original or former name of a member entity before any renaming or changes.
-
B.
namedMember
Indicates that an entity is a member of a group, organization, or collection and is identified by a specific name within that membership context.
-
C.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
D.
member2CurrentName
Indicates that the second member entity is associated with its current (most recent or active) name.
-
E.
member3CurrentName
Indicates that an entity’s currently used name is the third in a sequence of its known or recorded names.
- 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_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 3:13 p.m.