Triple
T29694155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | isBPSObject |
P167607
|
FINISHED |
| Object | yes, in appropriate backgrounds |
—
|
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, in appropriate backgrounds | Statement: [M2-branes, isBPSObject, yes, in appropriate backgrounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBPSObject Context triple: [M2-branes, isBPSObject, yes, in appropriate backgrounds]
-
A.
isBoson
Indicates that the subject is a boson, i.e., a particle that follows Bose–Einstein statistics and typically mediates forces or can occupy the same quantum state as others.
-
B.
isBinary
Indicates that the related entity or value has exactly two possible states, options, or components.
-
C.
isClassicalObjectIn
Indicates that a classical (non-quantum) object is located within or belongs to a specified region, context, or system.
-
D.
isCentralObjectIn
Indicates that an entity serves as the primary or focal object within a specified context, structure, or collection.
-
E.
isBSideOf
Indicates that one entity is located on the B side or secondary face of another entity, typically in a two-sided or dual-orientation context.
- 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_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:19 p.m.