Triple
T20690393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SO(32) heterotic string theory |
E508535
|
entity |
| Predicate | isAnomalyFree |
P82927
|
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: [SO(32) heterotic string theory, isAnomalyFree, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAnomalyFree Context triple: [SO(32) heterotic string theory, isAnomalyFree, true]
-
A.
hasAnomaly
Indicates that an entity exhibits, contains, or is associated with an irregular, abnormal, or unexpected condition or feature.
-
B.
isNormalIn
Indicates that one group is a normal subgroup of another group, meaning it is invariant under conjugation by elements of the larger group.
-
C.
isModelFree
Indicates that the behavior, decision, or control process does not rely on an internal model of the environment’s dynamics, but instead uses direct value estimates or cached experiences.
-
D.
hasNoIssue
chosen
Indicates that there are no problems, defects, or conflicts associated with the referenced entity or situation.
-
E.
isIceFree
Indicates that a location, surface, or object is not covered by ice or free from ice presence.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10cb5588190acb88f2c82fc593a |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:08 p.m.