Triple
T23737940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heterotic supergravity |
E586586
|
entity |
| Predicate | alternativeFrame |
P124922
|
FINISHED |
| Object | Einstein frame |
—
|
NE NERFINISHED |
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: Einstein frame | Statement: [heterotic supergravity, alternativeFrame, Einstein frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeFrame Context triple: [heterotic supergravity, alternativeFrame, Einstein frame]
-
A.
usesFrame
chosen
Indicates that one entity employs, relies on, or is structured around a particular frame, framework, or reference structure provided by another entity.
-
B.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
-
C.
framed
Indicates that one entity has been falsely presented or set up to appear responsible or guilty for an action or situation, typically to mislead others.
-
D.
alternativeFlag
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
-
E.
alternativeHolder
Indicates that one entity serves as an alternative or substitute holder in place of another entity.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.