Triple
T29694176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | hasElectricCouplingTo |
P135728
|
FINISHED |
| Object | 3-form potential C_3 |
—
|
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: 3-form potential C_3 | Statement: [M2-branes, hasElectricCouplingTo, 3-form potential C_3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricCouplingTo Context triple: [M2-branes, hasElectricCouplingTo, 3-form potential C_3]
-
A.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
B.
isElectrically
chosen
Indicates that one entity has an electrical property, connection, or interaction in relation to another entity.
-
C.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
hasCouplingConstant
Indicates that one entity is associated with a specific coupling constant value that quantifies the strength of an interaction or relationship.
-
E.
hasElectricalProperty
Indicates that an entity possesses a specific electrical characteristic or behavior, such as conductivity, resistance, or charge-related properties.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 7:19 p.m.