Triple
T27733285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IFormatProvider |
E697477
|
entity |
| Predicate | isAbstractMemberSet |
P145275
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.IFormatProvider, isAbstractMemberSet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAbstractMemberSet Context triple: [System.IFormatProvider, isAbstractMemberSet, true]
-
A.
hasNonConstituentMember
Indicates that an entity includes a member or component that is not formally recognized as a constituent part of it.
-
B.
isOnlyExtantMemberOf
Indicates that an entity is the sole surviving or currently existing member of a particular group, lineage, or category.
-
C.
onlyConstantMemberOf
Indicates that an entity is the sole constant (unchanging) member of a particular group, set, or collection.
-
D.
hasAbstractType
chosen
Indicates that an entity is associated with or classified under a more general, conceptual type rather than a concrete or specific instance.
-
E.
isNonStatutoryMemberClass
Indicates that a given class of members belongs to a category that is not defined or mandated by statute or formal legislation.
- 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_69f6369e16a08190853fdd8ac05800f6 |
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:12 p.m.