Triple
T29694200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5-branes |
E751297
|
entity |
| Predicate | BPSProperty |
P167611
|
FINISHED |
| Object | 1/2-BPS state in M-theory |
—
|
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/2-BPS state in M-theory | Statement: [M5-branes, BPSProperty, 1/2-BPS state in M-theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BPSProperty Context triple: [M5-branes, BPSProperty, 1/2-BPS state in M-theory]
-
A.
basisProperty
Indicates that one property serves as the foundational or defining basis for another property or characteristic.
-
B.
targetProperty
Indicates that one entity serves as the intended goal, focus, or object of another entity’s action, influence, or effect.
-
C.
protocolProperty
Indicates that a specific property or characteristic is defined or governed by a particular protocol.
-
D.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
-
E.
numericalProperty
Indicates that an entity is associated with a specific numeric value or measurable quantity.
- 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.