Triple
T27732936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Enum |
E697471
|
entity |
| Predicate | cannotBeBaseFor |
P38827
|
FINISHED |
| Object | Non-enum types |
—
|
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: Non-enum types | Statement: [System.Enum, cannotBeBaseFor, Non-enum types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeBaseFor Context triple: [System.Enum, cannotBeBaseFor, Non-enum types]
-
A.
cannotBeInheritedAs
Indicates that a property, method, or characteristic of one entity is not allowed to be passed down or inherited by another entity.
-
B.
cannotBeCastBy
Indicates that a particular action, spell, or effect is not allowed to be performed or initiated by a specified entity.
-
C.
cannotBeConstructedWith
Indicates that one entity cannot be created, formed, or assembled using the other entity or set of entities as components, resources, or methods.
-
D.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
E.
notDerivedFrom
chosen
Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 3:12 p.m.