Triple
T27732664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Single |
E697466
|
entity |
| Predicate | hasStaticField |
P189711
|
FINISHED |
| Object | MinValue |
—
|
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: MinValue | Statement: [System.Single, hasStaticField, MinValue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStaticField Context triple: [System.Single, hasStaticField, MinValue]
-
A.
isStatic
Indicates that the referenced entity does not change over time or across instances and remains fixed in its context.
-
B.
isStaticallyTyped
Indicates that a programming language enforces type checking at compile time rather than at runtime.
-
C.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
D.
hasStrongField
Indicates that one entity possesses or exhibits a powerful or intense field (such as a physical, electromagnetic, or influence field) relative to some context or standard.
-
E.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
- 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_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 27, 2026, 3:12 p.m.