Triple
T29694225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5-branes |
E751297
|
entity |
| Predicate | worldvolumeSignature |
P192772
|
FINISHED |
| Object | (1,5) |
—
|
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: (1,5) | Statement: [M5-branes, worldvolumeSignature, (1,5)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldvolumeSignature Context triple: [M5-branes, worldvolumeSignature, (1,5)]
-
A.
worldvolumeDimension
Indicates the number of dimensions of the extended space (worldvolume) in which an object or brane exists or evolves.
-
B.
worldvolumeAnomalies
Indicates that certain anomalies arise on the extended worldvolume of a brane or object, typically signaling inconsistencies or required modifications in the associated physical or gauge theory.
-
C.
worldNumber
Indicates the specific world, dimension, or universe identifier associated with an entity or event.
-
D.
stackWorldvolumeTheory
Indicates a relationship where one worldvolume theory is formed by stacking or combining multiple constituent worldvolume theories.
-
E.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: April 28, 2026, 7:19 p.m.