Triple
T29694120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | worldsheetHasCrosscaps |
P192295
|
FINISHED |
| Object | 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: yes | Statement: [Type I string theory, worldsheetHasCrosscaps, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldsheetHasCrosscaps Context triple: [Type I string theory, worldsheetHasCrosscaps, yes]
-
A.
orientabilityCriterion
Indicates the condition or rule that determines whether a given object, structure, or space is orientable.
-
B.
forSurfaceOfGenus
Indicates that one entity is the surface associated with or belonging to a particular genus.
-
C.
hasUniversalCoverTopology
Indicates that one space is equipped with the topology inherited from, or corresponding to, its universal covering space.
-
D.
worldsheetConformalInvariance
Indicates that a string theory configuration preserves conformal invariance on the worldsheet, meaning the worldsheet dynamics are invariant under local angle-preserving (conformal) transformations.
-
E.
hasAlternativeCrossing
Indicates that there exists another available crossing option that can be used instead of the primary one.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 28, 2026, 7:19 p.m.