Triple
T27732934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Enum |
E697471
|
entity |
| Predicate | underlyingTypeConstraint |
P64496
|
FINISHED |
| Object | Integral types only |
—
|
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: Integral types only | Statement: [System.Enum, underlyingTypeConstraint, Integral types only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingTypeConstraint Context triple: [System.Enum, underlyingTypeConstraint, Integral types only]
-
A.
elementTypeConstraint
Indicates that there is a restriction or rule specifying which types of elements are allowed or required in a given context.
-
B.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
C.
hasTypeOfRestriction
chosen
Indicates that an entity is subject to a specific kind or category of restriction that limits its use, access, or behavior.
-
D.
hasConstraintArity
Indicates that a constraint is associated with a specific number of arguments or elements it applies to.
-
E.
hasUnderlyingEntity
Indicates that one entity serves as the fundamental or base entity upon which another entity is conceptually or structurally built.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 3:12 p.m.