Triple
T20690395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SO(32) heterotic string theory |
E508535
|
entity |
| Predicate | leftMovingSector |
P141065
|
FINISHED |
| Object | supersymmetric |
—
|
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: supersymmetric | Statement: [SO(32) heterotic string theory, leftMovingSector, supersymmetric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftMovingSector Context triple: [SO(32) heterotic string theory, leftMovingSector, supersymmetric]
-
A.
frontSector
Indicates that one entity is located in the forward-facing sector or region relative to another entity.
-
B.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
C.
leftPosition
Indicates that one entity is located to the left side of another entity in space or ordering.
-
D.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
E.
positionInSector
Indicates the specific location or placement of an entity within a defined sector or sub-area.
- 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_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. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:08 p.m.