Triple
T29694125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | isUVFinite |
P154405
|
FINISHED |
| Object | conjecturally yes |
—
|
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: conjecturally yes | Statement: [Type I string theory, isUVFinite, conjecturally yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUVFinite Context triple: [Type I string theory, isUVFinite, conjecturally yes]
-
A.
isFiniteOver
Indicates that one mathematical structure is a finite extension or has finite degree/size when considered over another underlying structure.
-
B.
finiteAt
Indicates that a function, quantity, or value remains finite (not infinite or undefined) at a specified point or under a given condition.
-
C.
hasFiniteSupport
Indicates that a function, relation, or structure is nonzero or nontrivial at only finitely many elements of its domain.
-
D.
hasUVBehavior
chosen
Indicates that one entity exhibits or is characterized by a specific behavior or response when exposed to ultraviolet (UV) conditions.
-
E.
isFinite
Indicates that the value, set, or quantity in question is limited in size or extent and does not continue indefinitely.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:19 p.m.