Triple
T33511870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | graphene |
E858270
|
entity |
| Predicate | bondAngle |
P133697
|
FINISHED |
| Object | 120 degrees (approximately) |
—
|
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: 120 degrees (approximately) | Statement: [graphene, bondAngle, 120 degrees (approximately)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondAngle Context triple: [graphene, bondAngle, 120 degrees (approximately)]
-
A.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
-
B.
keyAngle
Indicates the angular orientation or rotation of a key relative to a reference position or axis.
-
C.
hasDihedralAngle
Indicates that there is a specific angle formed between two intersecting planes or faces.
-
D.
leanAngle
Indicates the degree to which an entity is tilted or inclined away from a reference upright position.
-
E.
hasTypicalAngle
chosen
Indicates that there is a characteristic or commonly occurring angle associated with the relationship between the entities.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:38 a.m.