Triple
T29694092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type I string theory |
E751295
|
entity |
| Predicate | worldsheetOrientation |
P192143
|
FINISHED |
| Object | unoriented |
—
|
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: unoriented | Statement: [Type I string theory, worldsheetOrientation, unoriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldsheetOrientation Context triple: [Type I string theory, worldsheetOrientation, unoriented]
-
A.
workOrientation
Indicates the manner or attitude with which an entity approaches and performs its work or job-related activities.
-
B.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
-
C.
ringOrientation
Indicates the spatial alignment or facing direction of a ring relative to a reference frame or object.
-
D.
valueOrientation
Indicates how an entity’s preferences, priorities, or attitudes are directed toward particular values or value systems.
-
E.
bandOrientation
Indicates the relative directional alignment or positioning of one band with respect to another or to a reference frame.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 28, 2026, 7:19 p.m.