Triple
T27732712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.SByte |
E697467
|
entity |
| Predicate | hasDefaultValue |
P128025
|
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.SByte, hasDefaultValue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefaultValue Context triple: [System.SByte, hasDefaultValue, true]
-
A.
hasZeroDefaultValue
Indicates that the associated entity or attribute is defined to have a default value of zero when no explicit value is provided.
-
B.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
defaultValue
chosen
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
D.
isDefaultFor
Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
-
E.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
- 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_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 3:12 p.m.