Triple
T27732926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Enum |
E697471
|
entity |
| Predicate | isGenericType |
P163132
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [System.Enum, isGenericType, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGenericType Context triple: [System.Enum, isGenericType, false]
-
A.
isGenericOver
Indicates that one entity is defined or parameterized in terms of another, more specific entity, such that it can operate over or apply to that entity as a generic.
-
B.
isGenericAvailable
Indicates that a non-brand (generic) version of a product, typically a medication, is available as an alternative.
-
C.
isGenericConstraintExample
Indicates that one entity serves as an example or illustration of a generic type constraint applied to another entity.
-
D.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
E.
hasGenericName
Indicates that an entity is associated with a non-brand, generic name that designates its general type or class.
- 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_69f6369e16a08190853fdd8ac05800f6 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:12 p.m.